Date: Tue, 12 Dec 2000 10:50:59 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Mark Huizer <freebsd@dohd.org> Cc: Alfred Perlstein <bright@wintelcom.net>, Dag-Erling Smorgrav <des@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/etc crontab Message-ID: <20001212105059.A766@gray.westgate.gr> In-Reply-To: <20001211182239.B20131@eeyore.local.dohd.org>; from freebsd@dohd.org on Mon, Dec 11, 2000 at 06:22:40PM %2B0100 References: <200012101254.eBACsZu99303@freefall.freebsd.org> <20001210052846.E16205@fw.wintelcom.net> <20001210171009.B1675@hades.hell.gr> <20001211182239.B20131@eeyore.local.dohd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 11, 2000 at 06:22:40PM +0100, Mark Huizer wrote: ... > > This will make sure that the succession of scripts will start at 03:01 > > and run (in this order), daily -> weekly -> monthly. The rules that I > > followed are: ... > > Isn't it kind of easier to let periodic use a lock in /var/lock or > something and synchronize that way? After all the discussion with lock files, I am not sure there is a `correct' way to make sure than a crontab entry can lock out others or have them put in a queue. I seem to prefer letting cron do the checking and scheduling of jobs. I am re-reading through the thread of the lockfiles though, to see if I can come up with something that will use lockfiles only for running `periodic daily'. If daily takes more than a full day on a machine to run, it will probably fire up a second time before the first one finishes, if crontab doesn't use lockfiles. On the other hand, on a machine where daily takes more than a day to run, well.. there will eventually appear other problems too. - 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?20001212105059.A766>