Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2018-01-26 | Update 2018 copyright | xmr-eric | 1 | -1/+1 | |
2017-11-14 | Merge pull request #2696 | Riccardo Spagni | 1 | -0/+1 | |
937e7f8a Initialize openssl on startup (moneromooo-monero) | |||||
2017-10-21 | Initialize openssl on startup | moneromooo-monero | 1 | -0/+1 | |
2017-10-09 | Fix an object lifetime bug in net load tests | moneromooo-monero | 1 | -4/+5 | |
The commands handler must not be destroyed before the config object, or we'll be accessing freed memory. An earlier attempt at using boost::shared_ptr to control object lifetime turned out to be very invasive, though would be a better solution in theory. | |||||
2017-02-21 | update copyright year, fix occasional lack of newline at line end | Riccardo Spagni | 1 | -1/+1 | |
2017-02-16 | switch to boost::thread for mingw build | Lee Clagett | 1 | -4/+4 | |
2017-01-16 | fixups in logging init calls, and add missing net context in a log | moneromooo-monero | 1 | -1/+1 | |
2017-01-16 | Change logging to easylogging++ | moneromooo-monero | 1 | -6/+1 | |
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-03-21 | Revert "Print stack trace upon exceptions" | moneromooo-monero | 1 | -1/+0 | |
Ain't nobody got time for link/cmake skullduggery. This reverts commit fff238ec94ac6d45fc18c315d7bc590ddfaad63d. | |||||
2016-03-19 | Print stack trace upon exceptions | moneromooo-monero | 1 | -0/+1 | |
Useful for debugging users' logs | |||||
2016-02-22 | move g_test_dbg_lock_sleep from a global to a function level static | moneromooo-monero | 1 | -2/+0 | |
This avoids the need to define that variable in every program which uses epee. | |||||
2015-12-31 | updated copyright year | Riccardo Spagni | 1 | -1/+1 | |
2015-04-10 | [fix] log level change. compilation: dns, tests | rfree2monero | 1 | -1/+6 | |
old unbound #warning does not block compilation unit tests build fine. Even though the RPC/P2P network type is required again | |||||
2015-02-24 | 2014 network limit 1.3 fix log/path/data +utils | rfree2monero | 1 | -0/+3 | |
+toc -doc -drmonero Fixed the windows path, and improved logging and data (for graph) logging, fixed some locks and added more checks. Still there is a locking error, not added by my patches, but present in master version (locking of map/list of peers). | |||||
2015-02-20 | 2014 network limit 1.0a +utils +toc -doc -drmonero | rfree2monero | 1 | -0/+3 | |
commands and options for network limiting works very well e.g. for 50 KiB/sec up and down ToS (QoS) flag peer number limit TODO some spikes in ingress/download TODO problems when other up and down limit added "otshell utils" - simple logging (with colors, text files channels) | |||||
2015-01-02 | year updated in license | Riccardo Spagni | 1 | -1/+1 | |
2014-07-23 | License updated to BSD 3-clause | fluffypony | 1 | -3/+29 | |
2014-04-02 | json rpc for wallet and bugfix | Antonio Juarez | 1 | -1/+1 | |
2014-03-20 | some fixes | Antonio Juarez | 1 | -2/+5 | |
2014-03-03 | moved all stuff to github | Antonio Juarez | 1 | -0/+603 | |