From owner-freebsd-stable Fri Nov 3 9:15:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from core.atomicbluebear.org (core.atomicbluebear.org [64.4.83.19]) by hub.freebsd.org (Postfix) with ESMTP id 50B2737B4D7 for ; Fri, 3 Nov 2000 09:15:36 -0800 (PST) Received: (qmail 66122 invoked by uid 1001); 3 Nov 2000 17:15:27 -0000 Date: Fri, 3 Nov 2000 11:15:26 -0600 (CST) From: Michael Lea To: Bohdan Tashchuk Cc: Vivek Khera , stable@FreeBSD.ORG Subject: Re: REMINDER: 4.2 code freeze starts tomorrow! In-Reply-To: <3A029A6B.FFE15663@easystreet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 3 Nov 2000, Bohdan Tashchuk wrote: > Also for some silly reason I thought that the OpenBSD people might be > "smarter" about this. But no, their daily script runs at 1:30 and so > probably has the very same problem. The OpenBSD people *are* smarter about this. From the OpenBSD man page for cron(8): Special considerations exist when the clock is changed by less than 3 hours; for example, at the beginning and end of Daylight Saving Time. If the time has moved forward, those jobs which would have run in the time that was skipped will be run soon after the change. Conversely, if the time has moved backward by less than 3 hours, those jobs that fall into the repeated time will not be run. - Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message