[tor-bugs] #28761 [Core Tor/sbws]: sbws ignores config option `to_syslog`

[Tor Bug Tracker & Wiki]

#28761: sbws ignores config option `to_syslog`
---------------------------+-----------------------------------
 Reporter:  anadahz        |          Owner:  (none)
     Type:  defect         |         Status:  needs_review
 Priority:  Medium         |      Milestone:  sbws: 1.0.x-final
Component:  Core Tor/sbws  |        Version:  sbws: 1.0.2
 Severity:  Major          |     Resolution:
 Keywords:                 |  Actual Points:
Parent ID:                 |         Points:
 Reviewer:  nickm          |        Sponsor:
---------------------------+-----------------------------------

Comment (by juga):

 Replying to [comment:10 anadahz]:
 > Replying to [comment:7 juga]:
 > > Replying to [comment:6 anadahz]:
 > > > Replying to [comment:5 juga]:
 > > > > Correct, so why do you say it's ignoring it?. Is it logging to
 syslog?
 > > >
 > > > It is logging to syslog although it shouldn't.
 > >
 > > I see the ansible role is using systemd, that's the reason, systemd
 logs to journalctl and syslog what is the standard output.
 > > So, i'll document that, and set different log levels for the different
 outputs by default.
 >
 > The ansible role of sbws is heavily influenced by the Debian package
 which also uses a [https://salsa.debian.org/pkg-privacy-
 team/sbws/blob/debian/master/debian/sbws.service | systemd service].
 >
 > Which is the recommended way to run sbws?

 The recommended way is indeed doing as the Debian package does, ie,
 launching it with systemd.
 Just know that you will see stdout log in syslog, even if you don't
 configure to log to syslog.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28761#comment:13>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online