Am Fr, den 27.01.2006 schrieb STYMA, ROBERT E (ROBERT) um 21:25: > [styma8]: tail /var/log/messages > Jan 27 12:45:01 styma8 crond(pam_unix)[14334]: session closed for user root > Jan 27 12:46:01 styma8 rpc.mountd: authenticated unmount request from styma9:934 for /home (/home) > Jan 27 13:00:02 styma8 crond(pam_unix)[14410]: session opened for user root by (uid=0) > Jan 27 13:00:02 styma8 crond(pam_unix)[14410]: session closed for user root > Jan 27 13:01:01 styma8 crond(pam_unix)[14427]: session opened for user root by (uid=0) > Jan 27 13:01:01 styma8 crond(pam_unix)[14427]: session closed for user root > Jan 27 13:05:01 styma8 crond(pam_unix)[14448]: session opened for user root by (uid=0) > Jan 27 13:05:02 styma8 crond(pam_unix)[14448]: session closed for user root > Jan 27 13:15:01 styma8 crond(pam_unix)[21672]: session opened for user root by (uid=0) > Jan 27 13:15:01 styma8 crond(pam_unix)[21672]: session closed for user root [ a lot snipped ] In short: you want to not get the above loggings in the messages syslog file. > Robert E. Styma It is not facility cron causing these log entries. You need to exclude auth.=info to be logged into the messages file. So add auth.!=info to the syslog config line for the /var/log/messages target. It may be clever to direct auth.=info into its own log file. 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.35_FC2smp Serendipity 21:59:15 up 54 days, 2:36, load average: 1.28, 1.28, 0.79
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
