Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Oct 2012 16:26:21 -0700
From:      Adrian Chadd <adrian@freebsd.org>
To:        Eitan Adler <eadler@freebsd.org>
Cc:        svn-src-head@freebsd.org, Maxim Sobolev <sobomax@freebsd.org>, svn-src-all@freebsd.org, src-committers@freebsd.org
Subject:   Re: svn commit: r241576 - in head/usr.sbin/cron: cron crontab lib
Message-ID:  <CAJ-VmomTAPAOGjdJ8UZyY=mfnhbMAexyr_Fz9DMNqiyzDV0_fQ@mail.gmail.com>
In-Reply-To: <CAF6rxgn9DcwqnZW4uwS8OLmKMbs3Fg9x8o50KWzDunLS_H-tDA@mail.gmail.com>
References:  <201210150821.q9F8Lobc047576@svn.freebsd.org> <CAJ-VmomRx_n6LoXeQCPAX-KzVYqPcjhZt1J0MX89FiEEojPePw@mail.gmail.com> <CAF6rxgn9DcwqnZW4uwS8OLmKMbs3Fg9x8o50KWzDunLS_H-tDA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 15 October 2012 16:10, Eitan Adler <eadler@freebsd.org> wrote:
> On 15 October 2012 18:45, Adrian Chadd <adrian@freebsd.org> wrote:
>> Why not sleep for the amonut of time needed before the next event?
>
> If the crontab changes in the meantime. If the next event is in a week,
> but you modify the crontab, you don't want to sleep until next event.

Right. So "check the crontab file" event is also an event with a
timestamp in the future.

Maybe crontab should be using a command via a socket to reload, rather
than stat'ing files..


Adrian


> Why we stat the file every quantum instead of using something kqueue is
> a different question.
>
>
> --
> Eitan Adler
> Source & Ports committer
> X11, Bugmeister, Ports Security teams



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomTAPAOGjdJ8UZyY=mfnhbMAexyr_Fz9DMNqiyzDV0_fQ>