Date: Sun, 10 Dec 2000 22:18:29 -0800 From: "David O'Brien" <obrien@FreeBSD.org> To: James FitzGibbon <james@ehlo.com> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc crontab Message-ID: <20001210221829.C84706@dragon.nuxi.com> In-Reply-To: <20001210234818.A73780@ehlo.com>; from james@ehlo.com on Sun, Dec 10, 2000 at 11:48:18PM -0500 References: <rwatson@FreeBSD.org> <200012110043.eBB0hYV06366@hak.lan.Awfulhak.org> <20001210165229.A84706@dragon.nuxi.com> <20001210234818.A73780@ehlo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 10, 2000 at 11:48:18PM -0500, James FitzGibbon wrote:
> What about putting a variable in rc.conf (is that the right place for
> non-startup-related variables?) that represents the timeout value. Have it
> default to 0 (or some other acceptable limit). That gives acceptable
> behaviour plus an easily accessible place for admins to increase or even
> remove the timeout.
This would change the existing behavior in that `weekly' may not run if
`daily' hangs. The commit that started all this just gave more time to
`daily' before `weekly' ran -- but did not revent overlap of the two (was
we never have). I'm not sure preventing `weekly' from running is the
right thing. I guess we really want the "lockf" solution, but if the
lock wasn't gotten after the timeout, run anyway.
--
-- David (obrien@FreeBSD.org)
GNU is Not Unix / Linux Is Not UniX
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?20001210221829.C84706>