On 08/20, Leonid Isaev wrote:
>
> This changelog says that:
> * journald will no longer forward all local data to another running syslog
> daemon. This change has been made because rsyslog (which appears to be the
> most commonly used syslog implementation these days) no longer makes use of
> this, and instead pulls the data out of the journal on its own. Since
> forwarding the messages to a non-existent syslog server is more expensive
> than we assumed we have now turned this off. If you run a syslog server that
> is not a recent rsyslog version, you have to turn this option on again
> (ForwardToSyslog= in journald.conf).
>
> This is going to break syslog-ng... So is it possible to patch journald.conf
> and enable ForwardToSyslog in the package?
>
> Thanks,
It seems this is just a change in the default settings, nothing more. Right now
journald.conf contains two defaults that will be affected by this:
- Storage=auto
- ForwardToSyslog=yes
"Storage=auto" means journald will only record logging data to the systemd
journal if the directory /var/log/journal exists; "ForwardToSyslog=yes" means
journald will forward all data to any existing system logger such as syslog-ng
regardless of whether there's a system logger running or not, and regardless
of whether the systemd journal is saved or not. The update just means that from
now on, the default is the opposite---the systemd journal is enabled by default,
log forwarding is not. Just switch it back to your preferred logging method.
--
"A common mistake that people make when trying to design something completely
foolproof is to underestimate the ingenuity of complete fools." - Douglas Adams
