Date: Tue, 4 Apr 1995 02:28:45 -0500 (CDT) From: Mike Pritchard <pritc003@maroon.tc.umn.edu> To: paul@isl.cf.ac.uk (Paul Richards) Cc: ghelmer@alpha.dsu.edu, freebsd-questions@FreeBSD.org Subject: Re: cron skipped jobs during ST->DST change Message-ID: <199504040728.CAA07834@mpp.com> In-Reply-To: <199504031700.SAA13590@isl.cf.ac.uk> from "Paul Richards" at Apr 3, 95 06:00:04 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> In reply to Guy Helmer who said > > > > 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. I've used systems in the past that got this all right. During either time change, every scheduled cron job was run once and only once as long as cron remained running during that magic hour. -- Mike Pritchard pritc003@maroon.tc.umn.edu "Go that way. Really fast. If something gets in your way, turn"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504040728.CAA07834>