On 5/16/11 1:07 PM, Philip Prindeville wrote: > On 5/15/11 1:13 PM, Lennart Poettering wrote: >> On Sun, 15.05.11 13:08, Philip Prindeville >> (philipp_s...@redfish-solutions.com) wrote: >> >>>> Lennart >>> >>> Ok, then I'm unclear. Should rsyslog be running? >>> >>> Because "chkconfig rsyslog --list" doesn't show any information, and >>> it doesn't seem to be running after reboot. >> >> The output this command generates should point you to the fact that the >> --list command is not supported on systemd: >> >> <snip> >> Note: This output shows SysV services only and does not include native >> systemd services. SysV configuration data might be overridden by >> native >> systemd configuration. >> </snip> >> >>> # chkconfig rsyslog --add >>> # chkconfig rsyslog on >>> >>> doesn't seem to do anything. Shouldn't it be on by default? >> >> Yes, it should be on by default. >> >> "systemctl enable rsyslog.service" or "chkconfig rsyslog on" should >> ensure that. >> >> When upgrading at the wrong time the conversion from sysv to systemd >> might not work properly and the service is not enabled after the >> upgrade. This should not be a problem however in the final release of >> F15. >> >> Lennart >> > > > Yeah, I did a "yum upgrade", "chkconfig rsyslog on", and rebooted and that > seems to have solved that problem. > > Now I'm just staring at the excessive logging from pam: > > May 16 00:33:36 localhost sshd[32609]: Accepted password for philipp from > 192.168.1.10 port 41603 ssh2 > May 16 06:33:36 localhost sshd[32610]: fatal: mm_request_receive: read: > Connection reset by peer > May 16 00:33:36 localhost sshd[32609]: pam_systemd(sshd:session): Moving new > user session for philipp into control group /user/philipp/12. > May 16 00:33:36 localhost sshd[32609]: pam_unix(sshd:session): session opened > for user philipp by (uid=0) > May 16 00:33:36 localhost sshd[32615]: Received disconnect from 192.168.1.10: > 11: disconnected by user > May 16 00:33:36 localhost sshd[32609]: pam_systemd(sshd:session): Moving > remaining processes of user session 12 of philipp into control group > /user/philipp/master. > May 16 00:33:36 localhost sshd[32609]: pam_unix(sshd:session): session closed > for user philipp > > > -Philip >
Forgot to add, also seeing these hourly: May 16 10:01:01 localhost /usr/sbin/crond[3473]: pam_systemd(crond:session): Moving new user session for root into control group /user/root/23. May 16 10:01:02 localhost /USR/SBIN/CROND[3473]: pam_systemd(crond:session): Moving remaining processes of user session 23 of root into control group /user/root/master. May 16 11:01:01 localhost /usr/sbin/crond[3642]: pam_systemd(crond:session): Moving new user session for root into control group /user/root/24. May 16 11:01:01 localhost /USR/SBIN/CROND[3642]: pam_systemd(crond:session): Moving remaining processes of user session 24 of root into control group /user/root/master. May 16 12:01:01 localhost /usr/sbin/crond[3925]: pam_systemd(crond:session): Moving new user session for root into control group /user/root/25. May 16 12:01:01 localhost /USR/SBIN/CROND[3925]: pam_systemd(crond:session): Moving remaining processes of user session 25 of root into control group /user/root/master. Other than the messages not being very useful and filling up /var/log/messages, why is there the case-conversion? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
