Is there a bug in 'cron'? I have checked two systems, both running
2.5.1. Both are Sparc 1000s. On both systems the root cron jobs
failed to run last night, although cron jobs for other users ran
normally.
The cron jobs were scheduled for 3:15 am and 4:05 am, so that they
should not have been lost in the 1-hour gap caused by the change to
daylight savings time. On the other hand, on both machines the
crontabs directory (the files in it) seem to have been read at 4:13
am. Is cron recognizing the time change 73 minutes late, and
skipping jobs that were carefully scheduled so that they would not be
missed? Will it run these jobs twice in the fall to make up?