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). Therefore, you won't get a pacnew file, and the new config will be quietly put in place, breaking existing installations for no valid technical reason. Anyway, let's not argue about the semantics, it's not a big deal of course. Hopefully, this thread saves someone a bit of hairpulling :) 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