Am Mo, den 30.05.2005 schrieb Gerry Doris um 17:30: > 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. The vixie-cron introduced with FC3 supports logging through PAM. > 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. Better not to suppress auth completely. Change /etc/syslog.conf: #*.info;mail.none;news.none;authpriv.none;cron.none /var/log/messages *.info;mail.none;news.none;authpriv.none;cron.none;auth.!=info /var/log/messages #The auth.info messages into a different log file. auth.info /var/log/auth.info service syslog restart You then have a separate log file with the cron caused auth loggings. Alexander -- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.27_FC2smp Serendipity 18:22:06 up 6 days, 16:59, load average: 0.16, 0.12, 0.12
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
