fixup! Add SyslogFacility option.

d0080ed1 · Alexander Færøy · 9c63da81 · d0080ed1 · d0080ed1
Commit d0080ed1 authored Mar 27, 2018 by Alexander Færøy
Hide whitespace changes
Inline Side-by-side

Showing with 5 additions and 5 deletions

changes/ticket25355 changes/ticket25355 +1 -2

doc/tor.1.txt doc/tor.1.txt +4 -3

No files found.
--- a/changes/ticket25355
+++ b/changes/ticket25355
  o Minor features (logging):
    - When logging to syslog, it is now possible to change the facility value by
-      setting the SyslogFacility entry in torrc. Fixes bug 25355.
-
+      setting the SyslogFacility entry in torrc. Closes ticket 25355.
--- a/doc/tor.1.txt
+++ b/doc/tor.1.txt
@@ -723,11 +723,12 @@ GENERAL OPTIONS
    If 1, Tor will overwrite logs at startup and in response to a HUP signal,
    instead of appending to them. (Default: 0)

-[[SyslogFacility]] **SyslogFacility** __facility__:
+[[SyslogFacility]] **SyslogFacility** __facility__::
    When logging to syslog this option sets the syslog facility value. This
    value affects all syslog-based Log entries. Consult the syslog(3) man page for
-    information about possible values available on your platform. Can not be
-    changed while tor is running. (Default: none)
+    information about possible values available on your platform. Note that you
+    might have to strip the LOG_-part of the names mentioned in syslog(3).
+    Can not be changed while tor is running. (Default: none)

 [[SyslogIdentityTag]] **SyslogIdentityTag** __tag__::
    When logging to syslog, adds a tag to the syslog identity such that