Description of problem: Following the commit of #705427, systemd now generates the following messages at Debug level: May 26 09:01:01 localhost /usr/sbin/crond[5136]: pam_systemd(crond:session): Moving new user session for root into control group /user/root/67. May 26 09:01:01 localhost /USR/SBIN/CROND[5136]: pam_systemd(crond:session): Moving remaining processes of user session 67 of root into control group /user/root/master. as a consequence of authpriv.* being logged to /var/log/secure. The fix is to raise this to "authpriv.info" instead. Version-Release number of selected component (if applicable): 5.7.9-2.fc15 How reproducible: Not necessary... a running f15 system should do this by default. Steps to Reproduce: 1. 2. 3. Actual results: Lots of the above logs (one every hour). Expected results: Nothing, as the above log messages are non-exceptional indications (i.e. normal behavior). Additional info: https://bugzilla.redhat.com/show_bug.cgi?id=705427
Tomáš, in bug 705427 I said: > I believe changing the rsyslog configuration should not be necessary. > pam_systemd should stop producing debug messages by default. This is the patch > I mentioned: > http://lists.freedesktop.org/archives/systemd-devel/2011-May/002531.html Please wait for Lennart's response before doing this change to the default rsyslog.conf.
(In reply to comment #1) > Tomáš, > > in bug 705427 I said: > > I believe changing the rsyslog configuration should not be necessary. > > pam_systemd should stop producing debug messages by default. This is the patch > > I mentioned: > > http://lists.freedesktop.org/archives/systemd-devel/2011-May/002531.html > > Please wait for Lennart's response before doing this change to the default > rsyslog.conf. Looking at that patch, it doesn't seem to touch rsyslog... in fact, it adds a gating variable to calling syslog() so that debugging messages can be turned off altogether (which is a bit odd, since the logging level also functions as the gating variable).
(In reply to comment #2) > Looking at that patch, it doesn't seem to touch rsyslog... Correct. > in fact, it adds a gating variable to calling syslog() so that debugging > messages can be turned off altogether Yes. The debug messages will be off by default. It's similar to other PAM modules in this regard. > (which is a bit odd, since the logging level also functions as > the gating variable). True, but is more efficient to stop emitting the messages altogether, than to wake syslog only to have them discarded (in the usual configuration).
systemd-26-4.fc15, which I have just submitted to updates-testing, does not log debug messages by default anymore. I recommend WONTFIX for this bug.