> Am So, den 29.05.2005 schrieb Gerry Doris um 17:48: > >> I had a nice stable FC2 system that been running for ages. I finally >> decided to upgrade yesterday to FC3 and have now managed to get pretty >> well >> everything working again. However, I do have one problem that I just >> can't >> find. >> >> I get the following messages occurring every 5min in my syslog: >> >> May 29 10:55:01 tiger crond(pam_unix)[5071]: session opened for user >> root by >> (uid=0) >> May 29 10:55:01 tiger crond(pam_unix)[5069]: session opened for user >> root by >> (uid=0) >> May 29 10:55:01 tiger crond(pam_unix)[5070]: session opened for user >> root by >> (uid=0) >> May 29 10:55:01 tiger crond(pam_unix)[5073]: session opened for user >> root by >> (uid=0) >> May 29 10:55:02 tiger crond(pam_unix)[5069]: session closed for user >> root >> May 29 10:55:04 tiger crond(pam_unix)[5071]: session closed for user >> root >> May 29 10:55:15 tiger crond(pam_unix)[5070]: session closed for user >> root >> May 29 10:55:33 tiger crond(pam_unix)[5073]: session closed for user >> root >> >> I've looked at crontab and crond and commented out anything that was >> running >> at 5min intervals without effect. Is this something that happens on FC3 >> or >> is there something still broken? Any pointers where else to look??? > > A process must be remaining, being called from cron (crontab -l -u root > || /etc/cron.d/). "tail -f /var/log/cron" could help you to find out. > > http://marc.theaimsgroup.com/?l=fedora-list&m=110077335618263&w=2 > > Alexander Thanks for your reply. In hind sight I see that the messages weren't errors but merely pam notices that root had started a process and then that process had ended. As pointed out in the link you provided this is new behaviour from the cron package used in FC2. I was able to track these processes back to tasks being kicked off every 5mins in cron. Matthew Miller suggested removing the pam session line for cron but that didn't work for me. I ended up removing auth notifications in syslog.conf. I'm not really happy with this solution but will use it until I can figure out something better.
