Date: Sun, 4 Apr 1999 14:29:50 -0400 (EDT) From: <scottd@cloud9.net> To: FreeBSD-gnats-submit@freebsd.org Subject: conf/10947: Problems entering daylight time Message-ID: <199904041829.OAA29881@earl-grey.cloud9.net>
next in thread | raw e-mail | index | archive | help
>Number: 10947 >Category: conf >Synopsis: Entering daylight time at 2am loses /etc/daily (or other 2am jobs) >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Apr 4 11:30:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Scott Drassinower >Release: FreeBSD 2.2.7-STABLE i386 >Organization: Cloud 9 Consulting, Inc. >Environment: 2.2.7-STABLE, also 3.1-RELEASE >Description: Daylight time (at least in the US) begins at 2am. By default, /etc/daily runs at 2am, so when the clock changes from 01:59 to 03:00, any cron jobs set to run at the 2am hour will get skipped. Every n minute jobs get skipped also, but that isn't as bad as having something that specifically runs at the 2am hour getting lost. I wonder how cron acts when we get the hour back in the fall. >How-To-Repeat: Install FreeBSD 2.2.7 or 3.1, wait for daylight time to begin, and see that /etc/daily or anything else that you have running between 02:00 and 02:59 on that day will not run. >Fix: Do not run things at 2am, and include a little note in the crontab file about this. It may not be a good idea to have cron go and rerun 02:00 to 02:59 missed jobs. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904041829.OAA29881>