Adam Beneschan wrote:
> On Mar 2, 4:36 pm, "Adam Beneschan" <a...@irvine.com> wrote:
>
>> Oh, well. Anyway, it looks like things did work fine. Thanks to
>> everyone for your help.
>
> OK, everything's working now---thanks again for all your help.
>
> I do have one more question. Assuming I don't reboot our systems any
> time between now and next week, what will happen with the cron
> daemons? Will they automatically adjust to the new time, or will I
> have to stop and restart them or do something else to refresh the time
> zone tables used by the Unix library routines, or something like that,
> so that it doesn't run everything an hour late? (It's not a disaster
> if it runs late, but some backup processes are scheduled so that they
> will complete before I come into work, and it will be a minor nuisance
> if they're still running.)
>
> -- thanks, Adam
>
Everything will be fine unless you try to start things around 2AM on
Sundays. In that case, they will be skipped this week, and run twice next
fall. I solve that by doing this in my /etc/crontab:

# Do not start things from 01:00 to 02:59 because they will run twice
# when the fall switch from daylight savings time to standard time occurs,
# and may be skipped in the spring when 2:00 AM is skipped.

#M H D m d user program arguments
01 * * * * root run-parts /etc/cron.hourly
04 1 * * 1-6 root run-parts /etc/cron.daily
04 3 * * 0 root run-parts /etc/cron.weekly
19 4 1 * * root run-parts /etc/cron.monthly


--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 21:30:01 up 19 days, 9:54, 3 users, load average: 4.25, 4.28, 4.20