Thomas R. Detman
Thomas.R.Detman at noaa.gov
Fri Feb 23 16:08:00 MST 2001
Thanks and I'm a little embarrased. I tried the suggestion; it did't
change what was going into "/var/log/messages", but it did lead me to
discover the man page for syslog.conf. The cause of the cron messages
going into /var/log/messages was the following line in syslog.conf:
I changed it to:
That fixed it. The suggested line causes all cron messages to go
into /var/log/cron, that's good since I stopped them from going into
> I would try adding this to syslog.conf to start with:
> cron.* /var/log/cron
> "Thomas R. Detman" wrote:
>> On Feb 14 I upgraded to KRUD 7.0+ (2000-11-03 version).
>> Ever since the following messages show up in "/var/log/messages" at
>> regular intervals. Every 10 minutes in the case of the "rmmod" message,
>> and houry, daily, monthly, etc for the others.
>> lines from /var/log/messages:
>> Feb 21 16:40:00 saturn CROND: (root) CMD ( /sbin/rmmod -as)
>> Feb 21 17:01:00 saturn CROND: (root) CMD (run-parts /etc/cron.hourly)
>> Feb 20 04:02:01 saturn CROND: (root) CMD (run-parts /etc/cron.daily)
>> These things are now the bulk of my system log file. How do I stop these
>> recurrent entries from being made? If I "su" and "run-parts /etc/cron.hourly"
>> no stdout or stderr is generated, and no e-mail is being sent to root.
>> No changes were made to my "/etc/syslog.conf" file, so it "appears" to have
>> something to do with going from KRUD 6.2 to 7.0.
More information about the LUG