wownero

Commit Graph

Author	SHA1	Message	Date
SomaticFanatic	5ef0607da6	Update copyright year to 2020 Update copyright year to 2020	4 years ago
moneromooo-monero	56a4469ef3	network: log traffic and add a simple traffic analysis script	4 years ago
binaryFate	1f2930ce0b	Update 2019 copyright	5 years ago
Riccardo Spagni	5ccd3d32b4	Merge pull request #4489 `00901e9c` epee: initialize a few data members where it seems to be appropriate (moneromooo-monero) `144a6c32` abstract_tcp_server2: move m_period to subclass (moneromooo-monero) `758d7684` connection_basic: remove unused floating time start time (moneromooo-monero) `e5108a29` Catch more exceptions in dtors (moneromooo-monero)	6 years ago
moneromooo-monero	e736964a0c	Remove epee header dependency on cryptonote_core	6 years ago
moneromooo-monero	e5108a294a	Catch more exceptions in dtors Misc coverity reports	6 years ago
Dimitris Apostolou	57c0b1ed9f	Fix typos in various files	6 years ago
xmr-eric	18216f19dd	Update 2018 copyright	6 years ago
Riccardo Spagni	8df6b010eb	Merge pull request #2696 `937e7f8a` Initialize openssl on startup (moneromooo-monero)	7 years ago
moneromooo-monero	937e7f8aa6	Initialize openssl on startup	7 years ago
moneromooo-monero	7dbf76d0da	Fix an object lifetime bug in net load tests 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.	7 years ago
Riccardo Spagni	c3599fa7b9	update copyright year, fix occasional lack of newline at line end	7 years ago
Lee Clagett	2cde2c02ca	switch to boost::thread for mingw build	7 years ago
moneromooo-monero	a480bf6b14	fixups in logging init calls, and add missing net context in a log	7 years ago
moneromooo-monero	5833d66f65	Change logging to easylogging++ 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.	7 years ago
moneromooo-monero	f7301c3563	Revert "Print stack trace upon exceptions" Ain't nobody got time for link/cmake skullduggery. This reverts commit `fff238ec94`.	8 years ago
moneromooo-monero	fff238ec94	Print stack trace upon exceptions Useful for debugging users' logs	8 years ago
moneromooo-monero	5e3557d2c3	move g_test_dbg_lock_sleep from a global to a function level static This avoids the need to define that variable in every program which uses epee.	8 years ago
Riccardo Spagni	de03926850	updated copyright year	9 years ago
rfree2monero	32c19c6c3d	[fix] log level change. compilation: dns, tests old unbound #warning does not block compilation unit tests build fine. Even though the RPC/P2P network type is required again	9 years ago
rfree2monero	0198ffb220	2014 network limit 1.3 fix log/path/data +utils +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).	9 years ago
Riccardo Spagni	f4b69d553a	year updated in license	10 years ago
fluffypony	6fc995fe5d	License updated to BSD 3-clause	10 years ago
Antonio Juarez	296ae46ed8	moved all stuff to github	10 years ago

24 Commits (master)