mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-24 04:13:28 +01:00
doc: Document the signal-safe log behaviour in the tor man page
Part of 31389.
This commit is contained in:
parent
e1429d9148
commit
102546f99f
@ -663,7 +663,16 @@ GENERAL OPTIONS
|
||||
debug, info, notice, warn, and err. We advise using "notice" in most cases,
|
||||
since anything more verbose may provide sensitive information to an
|
||||
attacker who obtains the logs. If only one severity level is given, all
|
||||
messages of that level or higher will be sent to the listed destination.
|
||||
messages of that level or higher will be sent to the listed destination. +
|
||||
+
|
||||
Some low-level logs may be sent from signal handlers, so their destination
|
||||
logs must be signal-safe. These low-level logs include backtraces,
|
||||
logging function errors, and errors in code called by logging functions.
|
||||
Signal-safe logs are always sent to stderr or stdout. They are also sent to
|
||||
a limited number of log files that are configured to log messages at error
|
||||
severity from the bug or general domains. They are never sent as syslogs,
|
||||
android logs, control port log events, or to any API-based log
|
||||
destinations.
|
||||
|
||||
[[Log2]] **Log** __minSeverity__[-__maxSeverity__] **file** __FILENAME__::
|
||||
As above, but send log messages to the listed filename. The
|
||||
|
Loading…
Reference in New Issue
Block a user