From owner-freebsd-bugs Sun Nov 19 14: 2:49 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from phalse.2600.com (phalse.2600.COM [216.66.24.2]) by hub.freebsd.org (Postfix) with ESMTP id 2579137B4C5; Sun, 19 Nov 2000 14:02:47 -0800 (PST) Received: from localhost (localhost [[UNIX: localhost]]) by phalse.2600.com (8.8.8/8.8.8) with ESMTP id RAA26143; Sun, 19 Nov 2000 17:02:46 -0500 (EST) Date: Sun, 19 Nov 2000 17:02:46 -0500 (EST) From: "H. ICHIKAWA" To: dougb@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org, opentrax@email.com Subject: Re: bin/22954: cron isn't daylight savings-aware In-Reply-To: <200011191807.KAA80689@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Your tell me not to schedule cron jobs during that time period, when the stock FreeBSD root crontab violates this principle. hmm.. > State-Changed-From-To: open->closed The problem persists. --Dominick On Sun, 19 Nov 2000 dougb@FreeBSD.org wrote: > Date: Sun, 19 Nov 2000 10:07:36 -0800 (PST) > From: dougb@FreeBSD.org > To: seraf@2600.com, dougb@FreeBSD.org, freebsd-bugs@FreeBSD.org > Subject: Re: bin/22954: cron isn't daylight savings-aware > > Synopsis: cron isn't daylight savings-aware > > State-Changed-From-To: open->closed > State-Changed-By: dougb > State-Changed-When: Sun Nov 19 10:04:52 PST 2000 > State-Changed-Why: > > The problems are actually much more complex than you describe. > Ultimately, the advice in crontab(5) should be heeded, namely > don't schedule jobs during that time period. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=22954 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message