Revert upstream commit
46b131574fdd7d77 for now, until Debian's sysloggers
can/do all read from the journal directly. See
http://lists.freedesktop.org/archives/systemd-devel/2014-November/025550.html
for details. Once we grow a journal.conf.d/ directory, sysloggers can be moved
to pulling from the journal one by one and disable forwarding again in such a
conf.d snippet.
Gbp-Pq: Topic debian
Gbp-Pq: Name Re-enable-journal-forwarding-to-syslog.patch
the system console, or sent as wall messages to all logged-in users. These
options take boolean arguments. If forwarding to syslog is enabled but nothing
reads messages from the socket, forwarding to syslog has no effect. By default,
- only forwarding to wall is enabled. These settings may be overridden at boot time
+ only forwarding to syslog and wall is enabled. These settings may be overridden at boot time
with the kernel command line options
<literal>systemd.journald.forward_to_syslog</literal>,
<literal>systemd.journald.forward_to_kmsg</literal>,
s->rate_limit_interval = DEFAULT_RATE_LIMIT_INTERVAL;
s->rate_limit_burst = DEFAULT_RATE_LIMIT_BURST;
+ s->forward_to_syslog = true;
s->forward_to_wall = true;
s->max_file_usec = DEFAULT_MAX_FILE_USEC;
#RuntimeMaxFiles=100
#MaxRetentionSec=
#MaxFileSec=1month
-#ForwardToSyslog=no
+#ForwardToSyslog=yes
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes