Date: Wed, 20 Dec 2000 21:16:57 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: "David E. O'Brien" <obrien@FreeBSD.ORG> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/etc crontab Message-ID: <20001220211656.B11175@hades.hell.gr> In-Reply-To: <200012111838.eBBIcrY50441@freefall.freebsd.org>; from obrien@FreeBSD.ORG on Mon, Dec 11, 2000 at 10:38:52AM -0800 References: <200012111838.eBBIcrY50441@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 11, 2000 at 10:38:52AM -0800, David E. O'Brien wrote:
> obrien 2000/12/11 10:38:52 PST
>
> Modified files:
> etc crontab
> Log:
> Revert back to rev 1.24 as we have not come to a consensus if is is OK
> for a hung `daily' run to keep a `weekly' run from happening.
...
As Mike Meyer showed to me in a very informative mail of his, the changes I
had proposed to /etc/crontab were flawed. To quote his words:
The reason I think so is that the crontab(5) man page says:
Note: The day of a command's execution can be specified by two fields --
day of month, and day of week. If both fields are restricted (ie, aren't
*), the command will be run when either field matches the current time.
By reading the sources of /usr/src/usr.sbin/cron/cron/cron.c I found out
that Mike is indeed doing the correct thing to quote the manpage, and that
both the manpage and the sources state the same fact clearly. Since then,
I haven't managed to find a replacement set of crontab entries to do the
intended thing (i.e. run periodic weekly only after daily finishes, and
monthly only after weekly finishes).
This is what happens when inadequate testing is done, I guess.
Thanks, Mike, for showing this to me :-)
- giorgos
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001220211656.B11175>