Date: Tue, 8 Apr 1997 14:09:07 +1000 (EST) From: Darren Reed <avalon@coombs.anu.edu.au> To: imp@village.org (Warner Losh) Cc: thompson@squirrel.tgsoft.com, hackers@freebsd.com Subject: Re: crontab nit? Message-ID: <199704080416.VAA14625@freefall.freebsd.org> In-Reply-To: <E0wEHXR-0000a9-00@rover.village.org> from "Warner Losh" at Apr 7, 97 10:45:01 am
next in thread | previous in thread | raw e-mail | index | archive | help
HP-UX man page for cron:
Notes
On the days of daylight savings (summer) time transition (in time
zones and countries where daylight savings time applies), cron
schedules commands differently than normal.
In the following description, an ambiguous time refers to an hour and
minute that occurs twice in the same day because of a daylight savings
time transition (usually on a day during the Autumn season). A non-
existent time refers to an hour and minute that does not occur because
of a daylight savings time transition (usually on a day during the
Spring season). DST-shift refers to the offset that is applied to
standard time to result in daylight savings time. This is normally
one hour, but can be any combination of hours and minutes up to 23
hours and 59 minutes (see tztab(4)).
When a command is specified to run at an ambiguous time, the command
is executed only once at the first occurrence of the ambiguous time.
When a command is specified to run a non-existent time, the command is
executed after the specified time by an amount of time equal to the
DST-shift. When such an adjustment would conflict with another time
specified to run the command, the command is run only once rather than
running the command twice at the same time.
For commands that are scheduled to run during all hours by specifying
a * in the hour field of the crontab entry, the command is scheduled
without any adjustment.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704080416.VAA14625>