From owner-freebsd-stable Sat Feb 21 14:51:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29691 for freebsd-stable-outgoing; Sat, 21 Feb 1998 14:51:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29617; Sat, 21 Feb 1998 14:50:18 -0800 (PST) (envelope-from danny@panda.hilink.com.au) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id JAA18242; Sun, 22 Feb 1998 09:50:14 +1100 (EST) Date: Sun, 22 Feb 1998 09:50:11 +1100 (EST) From: "Daniel O'Callaghan" To: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: /etc/crontab Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk It was written that /etc/daily is run twice or not at all during DST changes. I said it was a bug in cron(8); Archie Cobbs said it wasn't. HP-UX seems to have it sorted out.... Can anyone suggest an algorithm for implementing the HP-UX cron(8) behavior? Danny ---------- Forwarded message ---------- Date: Tue, 8 Apr 1997 14:09:07 +1000 (EST) From: Darren Reed To: Warner Losh Cc: thompson@squirrel.tgsoft.com, hackers@freebsd.com Subject: Re: crontab nit? 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message