Hi all, Anyone seen this? Sometimes cron (vixie-cron-3.0.1-61 RH 7.0) runs scheduled jobs twice, and sometimes even three times. This happens only two or three times a day, and only on one of the three machines I have running the same version of vixie-cron.
I thought that maybe the clock was being changed (by ntpdate) and causing the job to be run again. So, I now run ntpdate from a script at five minutes past the hour (rather than from /etc/cron./hourly at one minute past), and the script sleeps for ten seconds before running ntpdate. Clock updates are usually less than 0.2 seconds, and never more than 0.5. This should make it virtually impossible for the clock to move back far enough to run a job twice, especially one of those in /etc/cron.hourly which is started over four minutes before the clock is adjusted. Yet I'm still seeing jobs being run twice: Oct 29 03:05:10 wombat ntpdate[28814]: adjust time server 192.189.54.33 offset 0.184338 sec Oct 29 04:01:00 wombat CROND[28974]: (root) CMD (run-parts /etc/cron.hourly) Oct 29 04:01:59 wombat CROND[29027]: (root) CMD (run-parts /etc/cron.daily) Oct 29 04:02:00 wombat CROND[29089]: (root) CMD (run-parts /etc/cron.daily) Oct 29 04:05:11 wombat ntpdate[29572]: adjust time server 192.189.54.33 offset 0.182355 sec Oct 29 05:00:59 wombat CROND[29775]: (root) CMD (run-parts /etc/cron.hourly) Oct 29 05:01:01 wombat CROND[29808]: (root) CMD (run-parts /etc/cron.hourly) Oct 29 05:05:12 wombat ntpdate[29848]: adjust time server 192.189.54.33 offset 0.180785 sec Any ideas? Cheers, John -- whois [EMAIL PROTECTED] GPG key id: 0xD59C360F -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
