Bryan Phinney wrote: > > Actually, I am pretty sure that logrotate runs at midnight on Sunday for the > weekly logrotation. There can be actual commands associated with rotating > log files, for instance, Apache must be restarted after the logs are rotated. > > Other apps, depending on their pre and post command structure might run other > commands. > > The activity you see could be merely normal commands associated with rotating > logs of the apps that you have on your machine. > Logrotate is launched from /etc/cron.daily/logrotate. The executable files in this directory are executed by entry in /etc/crontab:
02 4 * * * root nice -n 19 run-parts /etc/cron.daily This is the default, and says run at 04:02 each day. Now, just because logrotate is run every day, that does not mean that all the logs are rotated every day. How often a log file is rotated is controlled by /etc/logrotate.conf. The default is set to weekly but is monthly for some logs. Now, if your timezone or clock settings are not set correctly, then the cron jobs may not run at the desired local times. One way to check this is to log at /var/log/cron/info, and compare the timestamp for the last cron.hourly to the current time. If the entry is something like: Jan 10 10:01:00 mikkel CROND[8911]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly) but the current time is "Tue Jan 10 12:22:38 CST 2006", and your machine is in the "central" time zone, you have a problem. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! ____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
