Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.10.2 2017-02-21T17:38:18Z 2017-02-21T17:38:18Z Riccardo Spagni ric@spagni.net 2017-02-21T17:38:18Z urn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359 2017-02-06T06:15:41Z Lee Clagett code@leeclagett.com 2017-02-05T22:48:03Z urn:sha1:ce7fcbb4aea884bb4bf433cf419ffa267f859c87 2017-01-22T11:37:55Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-01-22T11:37:55Z urn:sha1:4cdf0a35c94dac303fd703c05eb6685fc401a323 This prevents easy fingerprinting when you change IPs, and will be a must when kovri gets used. 2017-01-16T01:32:57Z Riccardo Spagni ric@spagni.net 2017-01-16T01:32:57Z urn:sha1:ab69d5b3670cc21a10aab9ad16919afdcc80fdba 16b8b66a specify restore height by YYYY-MM-DD format (kenshi84) 2017-01-16T01:00:28Z kenshi84 kenshi84@protonmail.ch 2016-12-25T08:18:15Z urn:sha1:16b8b66adcad57983b099fdf3ac1b52519390bc6 2017-01-16T00:25:46Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-01-01T16:34:23Z urn:sha1:5833d66f6540e7b34e10ddef37c2b67bd501994b This replaces the epee and data_loggers logging systems with a single one, and also adds filename:line and explicit severity levels. Categories may be defined, and logging severity set by category (or set of categories). epee style 0-4 log level maps to a sensible severity configuration. Log files now also rotate when reaching 100 MB. To select which logs to output, use the MONERO_LOGS environment variable, with a comma separated list of categories (globs are supported), with their requested severity level after a colon. If a log matches more than one such setting, the last one in the configuration string applies. A few examples: This one is (mostly) silent, only outputting fatal errors: MONERO_LOGS=*:FATAL This one is very verbose: MONERO_LOGS=*:TRACE This one is totally silent (logwise): MONERO_LOGS="" This one outputs all errors and warnings, except for the "verify" category, which prints just fatal errors (the verify category is used for logs about incoming transactions and blocks, and it is expected that some/many will fail to verify, hence we don't want the spam): MONERO_LOGS=*:WARNING,verify:FATAL Log levels are, in decreasing order of priority: FATAL, ERROR, WARNING, INFO, DEBUG, TRACE Subcategories may be added using prefixes and globs. This example will output net.p2p logs at the TRACE level, but all other net* logs only at INFO: MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE Logs which are intended for the user (which Monero was using a lot through epee, but really isn't a nice way to go things) should use the "global" category. There are a few helper macros for using this category, eg: MGINFO("this shows up by default") or MGINFO_RED("this is red"), to try to keep a similar look and feel for now. Existing epee log macros still exist, and map to the new log levels, but since they're used as a "user facing" UI element as much as a logging system, they often don't map well to log severities (ie, a log level 0 log may be an error, or may be something we want the user to see, such as an important info). In those cases, I tried to use the new macros. In other cases, I left the existing macros in. When modifying logs, it is probably best to switch to the new macros with explicit levels. The --log-level options and set_log commands now also accept category settings, in addition to the epee style log levels. 2016-12-17T11:28:49Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-12-17T11:25:15Z urn:sha1:55fa0479a0db599d81500e57e355124f1fb9c05e 2016-11-22T20:00:40Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-11-22T20:00:40Z urn:sha1:2c0173c722af7a6dc1f30c3423d97247a4fd1ad7 2016-10-31T08:38:00Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-10-28T20:19:40Z urn:sha1:e6deb8abda0b6560c8691f376d8a86aab163dd77 2016-10-10T21:19:36Z Dion Ahmetaj Dion Ahmetaj 2016-10-10T21:19:36Z urn:sha1:dd6c44327be7d90574466bc37561b9d156466972