torproject/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-12-06 19:41:15 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix log granularity based on Nick's comments.

Browse Source 
Instead of rejecting a value that doesn't divide into 1 second, round to
the nearest divisor of 1 second and warn.

Document that the option only controls the granularity written by Tor to a
file or console log. It does not (for example) "batch up" log messages to
affect times logged by a controller, times attached to syslog messages, or
the mtime fields on log files.
This commit is contained in:
Karsten Loesing
2010-11-08 16:37:20 +01:00
parent 8c5ba9388b
commit ed45bc198f
2 changed files with 27 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/tor.1.txt
+4 -1
View File
@@ -346,7 +346,10 @@ Other options can be specified either on the command-line (--option
**LogTimeGranularity** __NUM__::
Set the resolution of timestamps in Tor's logs to NUM milliseconds.
NUM must be positive and either a divisor or a multiple of 1 second.
(Default: 1 second)
Note that this option only controls the granularity written by Tor to
a file or console log. Tor does not (for example) "batch up" log
messages to affect times logged by a controller, times attached to
syslog messages, or the mtime fields on log files. (Default: 1 second)
**SafeLogging** **0**|**1**|**relay**::
Tor can scrub potentially sensitive strings from log messages (e.g.