monero.git - Monero: the secure, private, untraceable cryptocurrency

Age	Commit message (Collapse)	Author	Files	Lines
2017-12-16	move connection_basic and network_throttle from src/p2p to epee	moneromooo-monero	1	-369/+0
	These even had the epee namespace. This fixes some ugly circular dependencies.
2017-11-28	Corrections in rate limiting / trottle code, especially in 'out' direction	rbrunner7	1	-7/+1
	Deleted 3 out of 4 calls to method connection_basic::sleep_before_packet that were erroneous / superfluous, which enabled the elimination of a "fudge" factor of 2.1 in connection_basic::set_rate_up_limit; also ended the multiplying of limit values and numbers of bytes transferred by 1024 before handing them over to the global throttle objects
2017-07-31	some include cleanup	moneromooo-monero	1	-4/+4

2017-02-21	update copyright year, fix occasional lack of newline at line end	Riccardo Spagni	1	-1/+1

2017-02-13	network_throttle: demote spammy logs to TRACE	moneromooo-monero	1	-2/+2

2017-01-22	Remove boost/foreach.cpp includes	Miguel Herranz	1	-1/+0

2017-01-16	Change logging to easylogging++	moneromooo-monero	1	-11/+5
	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-11	Use boost::thread instead of std::thread	Howard Chu	1	-1/+1
	and all other associated IPC
2015-12-31	updated copyright year	Riccardo Spagni	1	-1/+1

2015-05-31	cleaning up, removing redundant files, renaming, fixing incorrect licenses	Riccardo Spagni	1	-1/+1

2015-05-17	s/terget/target/	moneromooo-monero	1	-1/+1

2015-04-01	remerged; commands JSON. logging upgrade. doxygen	rfree2monero	1	-3/+6

2015-02-20	2014 network limit 1.2 +utils +toc -doc -drmonero	rfree2monero	1	-2/+2
	new update of the pr with network limits more debug options: discarding downloaded blocks all or after given height. trying to trigger the locking errors. debug levels polished/tuned to sane values. debug/logging improved. warning: this pr should be correct code, but it could make an existing (in master version) locking error appear more often. it's a race on the list (map) of peers, e.g. between closing/deleting them versus working on them in net-limit sleep in sending chunk. the bug is not in this code/this pr, but in the master version. the locking problem of master will be fixed in other pr. problem is ub, and in practice is seems to usually cause program abort (tested on debian stable with updated gcc). see --help for option to add sleep to trigger the error faster.
2015-02-20	2014 network limit 1.1 +utils +toc -doc -drmonero	rfree2monero	1	-39/+36
	Update of the PR with network limits works very well for all speeds (but remember that low download speed can stop upload because we then slow down downloading of blockchain requests too) more debug options fixed pedantic warnings in our code should work again on Mac OS X and FreeBSD fixed warning about size_t tested on Debian, Ubuntu, Windows(testing now) TCP options and ToS (QoS) flag FIXED peer number limit FIXED some spikes in ingress/download FIXED problems when other up and down limit
2015-02-20	2014 network limit 1.0a +utils +toc -doc -drmonero	rfree2monero	1	-0/+382
	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)