Subject: Re: Turning off cron logging
From: Jim Cole (greyleaf@yggdrasill.net)
Date: Sat Oct 06 2001 - 20:28:39 MDT
Hi - Correcting myself :( If you want to get rid of the log
messages, you should probably go with cron.none instead of
cron.notice. Logging is already configured for cron to log
all priority messages into its own log file. Using
cron.notice worked for me at one point, but then failed to
do so later (probably something stupid on my part).
Jim
Jim Cole's bits of Sat, 6 Oct 2001 translated to:
>Paul J. Lucas's bits of Sat, 6 Oct 2001 translated to:
>
>> It's cron that's doing the logging, not rmmod.
>>
>>> >Oct 3 21:10:00 powerbook CROND[26785]: (root) CMD ( /sbin/rmmod -as)
>> ^^^^^
>
>Sorry. Should have paid more attention. The reason for the
>log message is a combination of crond itself and the
>settings in syslog.conf. It appears as if the version of
>crond distributed with YDL 2.0 makes a lot of noise at the
>..info level, which gets picked up by
>
> *.info;mail.none;news.none;authpriv.none
>
>in the /etc/syslog.conf file.
>
>To squash the log messages you are referring to (and all
>other .info messages from crond), change the syslog.conf
>file entry for /var/log/messages to
>
> *.info;cron.notice;mail.none;news.none;authpriv.none
>
>In this case, you shouldn't hear anymore from crond unless
>it is of priority 'notice' or higher.
>
>
>Jim
>
>
This archive was generated by hypermail 2a24 : Sat Oct 06 2001 - 19:39:53 MDT