Date: Thu, 06 Apr 2000 00:47:22 -0700 From: Doug Barton <Doug@gorean.org> To: dayton+freebsd-stable@overx.com Cc: Vivek Khera <khera@kciLink.com>, freebsd-stable@freebsd.org Subject: Re: dufus.[...] daily run output -- summer time Message-ID: <38EC4109.955BF5B@gorean.org> References: <14568.45040.795743.139682@kci.kciLink.com> <200004031510.LAB21697@radagast.wizard.net> <14568.47470.412562.32287@kci.kciLink.com> <86ya6v59om.fsf@polo.overx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Soren Dayton wrote:
>
> Vivek Khera <khera@kciLink.com> writes:
>
> > >>>>> "DRT" == Donald R Tyson <tyson@stanfordalumni.org> writes:
> >
> > DRT> At least the 4.0-STABLE side, despite the error reported by
> > DRT> several on this list, managed to get the time right.
> >
> > The error is in the date program's ability to tell you the time X
> > hours ago, when that X is during the leap-ahead hour. I consider this
> > a bug in date, as my example showed. The time exists, date just can't
> > tell you what it is.
>
> Also, I noticed that cron doesn't handle the leap-hour case.
Well, it does handle it, basically by ignoring it. This is not an
oversight however, it's essentially by design. When you start asking
yourself questions about what exactly it should do in those various
situations, you can quickly cause yourself a brain bleed. Much better to
handle the situation more appropriately by carefully scheduling your
cron jobs.
Doug
--
"So, the cows were part of a dream that dreamed itself into
existence? Is that possible?" asked the student incredulously.
The master simply replied, "Mu."
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38EC4109.955BF5B>