Re: TIME, DATE and CRON... trap for the unwary
Ian Perry <iperry@inertia.com.au> writes:
IP> Hi All,
IP> Just came across a point about Time and Date and CRON which could cause a
IP> problem for those who are unaware.
IP>
IP> If you have CRON running and you set back the Date or Time backwards, CRON
IP> will not run until at least the old time has been reached again.
IP>
IP> A quick reboot solves the problem.
...though it's almost never the right solution. I only reboot for
kernel upgrades and wedged kernel modules, generally. Running
'/etc/init.d/cron restart' as root will restart the cron daemon, and
hopefully get things running again.
This "problem" doesn't affect the normal boot process, even if you're
using ntpdate to get the current time off the network, since cron
starts fairly late in the normal boot sequence (/etc/rc2.d/S89cron).
Under "normal" circumstances, you don't need/want to move time
backwards anyways (it also confuses things like make that look at file
timestamps).
--
David Maze dmaze@debian.org http://people.debian.org/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
Reply to: