Date: Mon, 3 Apr 1995 18:00:04 +0100 (BST) From: Paul Richards <paul@isl.cf.ac.uk> To: ghelmer@alpha.dsu.edu (Guy Helmer) Cc: freebsd-questions@FreeBSD.org Subject: Re: cron skipped jobs during ST->DST change Message-ID: <199504031700.SAA13590@isl.cf.ac.uk> In-Reply-To: <Pine.OSF.3.91.950403094324.30033A-100000@alpha.dsu.edu> from "Guy Helmer" at Apr 3, 95 10:05:58 am
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Guy Helmer who said > > I just noticed that on Sunday, April 2 (the date of the Standard Time to > Daylight Savings Time change here in the U.S.) cron (under 1.1.5) missed > my /etc/daily jobs on all my systems with the default time of 2:00am for > the job. I'm not sure whether this is "correct" behavior or not... > > If cron hasn't been changed/fixed since 1.1.5, can we adjust the execution > time for /etc/daily in the default /etc/crontab to be earlier than 2:00am > (say, around 0:59am)? Or, perhaps this is "locale-specific" and we system > admins should know better than to leave cron jobs up to chance during time > changes; if this is the case, however, it would be nice to have a warning > in the crontab(5) man page... This is currently being discussed in the BSDI lists and the solution that struck me as sensible is to be able to specify that a cron job is executed at UST rather than local time. That'll guarantee it always gets run. There's also a problem when DST goes the other way in that the jobs get run twice. -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504031700.SAA13590>