[arch-general] [arch-dev-public] systemd 216 coming soon to testing

[Leonid Isaev]

On Thu, Aug 21, 2014 at 10:21:49AM -0500, Bigby James wrote:
> 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.

I know, but not everyone follows systemd-devel. So, just updating systemd would
lead to syslog "mysteriously" not logging anything...

[rant]
Besides, I don't understand the motivation that rsyslog "pulls the data out of
the journal on its own". If this is via the "imjournal" module, then
it's a bogus argument because even the official documentation basically
discourages the use of this module.
[/tant]

[1] http://www.rsyslog.com/doc/imjournal.html

Cheers,
-- 
Leonid Isaev
GPG fingerprints: DA92 034D B4A8 EC51 7EA6  20DF 9291 EE8A 043C B8C4
                  C0DF 20D0 C075 C3F1 E1BE  775A A7AE F6CB 164B 5A6D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://mailman.archlinux.org/pipermail/arch-general/attachments/20140821/d6d1e3ac/attachment.asc>