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

[Paul Gideon Dann]

On Thursday 21 Aug 2014 13:40:48 Leonid Isaev wrote:
> On Thu, Aug 21, 2014 at 11:56:06AM -0500, Bigby James wrote:
> > > > 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...
> > 
> > Sure, *if* you didn't already explicity set journald to use an external
> > logging daemon. If you did, then the update is just going to create a
> > *.pacnew file that can be deleted. In other words, the problem is
> > improper configuration on the part of the user, not impropriety on the
> > part of upstream.
> > 
> > I use syslog-ng myself, and it seems to me that if I'm going to be
> > deviating from the defaults set by upstream and the Arch devs then it
> > falls to me to pay
> Using syslog-ng is not "deviating from the defaults". So far the default was
> to send things to _a_ syslog -- no modification of journald.conf was
> required (check the old manpages).

If I remember correctly, when the switch to systemd was first made, the migration guide on 
the wiki did in fact talk the user through forwarding the journal to syslog-ng by modifying 
some config files.

Paul