Nick,
I could be wrong, but it would seem to me, that by adding the lock
files, the run-crons script could check to see if the previous cron
job was somehow still running. If it was still running it would not
start a new batch. Just a guess though, I'm not up on my shell
scripting... take a look at /usr/sbin/run-crons if you are.
-Mike Arrison
On Thu, Sep 25, 2003 at 11:22:33PM +0100, Nick Brown wrote:
> The current default gentoo crontab file is as below;
>
> <snip>
> */15 * * * * /usr/bin/test -x /usr/sbin/run-crons &&
> /usr/sbin/run-crons
> 0 * * * * rm -f /var/spool/cron/lastrun/cron.hourly
> 0 0 * * * rm -f /var/spool/cron/lastrun/cron.daily
> 0 0 * * 6 rm -f /var/spool/cron/lastrun/cron.weekly
> 0 0 1 * * rm -f /var/spool/cron/lastrun/cron.monthly
> <snip>
>
> What is the point/purpose of the run-crons script and its associated
> /var/spool/cron/ lock files?
> Why is the crontab not just something like below?
>
> <snip>
> 0 * * * * run-parts /etc/cron.hourly
> 0 0 * * * run-parts /etc/cron.daily
> 0 0 * * 6 run-parts /etc/cron.weekly
> 0 0 1 * * run-parts /etc/cron.monthly
> <snip>
>
> Cheers,
> Nick
>
>
> --
> [EMAIL PROTECTED] mailing list
pgp00000.pgp
Description: PGP signature
