On Thu, 15 Sep 2016 11:15:29 +0200 Matijs van Zuijlen <[email protected]> wrote: > Package: systemd > Version: 231-6 > Severity: normal > > Since recently, log messages from programs running under the gnome > session have started appearing in all logs in /var/logs, including > /var/logs/kern.log, even though my rsyslog configuration has not > changed, and correctly only routes kern.* there. > > This is very annoying since it fills the logs with messages that don't > belong there, and makes running logcheck tedious. > > It seems this is a recent regression, since before I was able to route > these messages to a low-priority log using the following rsyslog > configuration: > > user.=info;user.=notice;\ > user.=warn -/var/log/user-low.log > > If I look at the messages directly with journalctl -o verbose, it seems > they do not set the syslog facility, which should make them end up with > user facility, but doesn't.
I don't think this is a systemd bug per se, it just means that more GNOME/desktop components now directly log to the journal [¹]. In this case the syslog facility is not set, as you already noticed. Maybe glib should be updated to set the syslog facility to user, not sure. [¹] https://developer.gnome.org/glib/stable/glib-Message-Logging.html#g-log-structured -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
