Date: Fri, 03 Sep 2010 23:34:33 -0700 From: perryh@pluto.rain.com To: freebsd@qeng-ho.org Cc: gibblertron@gmail.com, freebsd-questions@freebsd.org Subject: Re: 8.1: Cron ignoring crontab updates Message-ID: <4c81e879.vT3c8HBQCXR5AwE5%perryh@pluto.rain.com> In-Reply-To: <4C80C1D6.2050104@qeng-ho.org> References: <AANLkTing=YCBQWYanuKa1NHBcBoCX6Fhyg=zGA%2BebtvA@mail.gmail.com> <AANLkTin0_9g_ngjPbPc69uUmUMU82HerbB5BORCckWkt@mail.gmail.com> <4c80af91.0XK7R1NzplpVQC/a%perryh@pluto.rain.com> <4C80C1D6.2050104@qeng-ho.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Arthur Chance <freebsd@qeng-ho.org> wrote: > On 09/03/10 09:19, perryh@pluto.rain.com wrote: > > Chris Rees<utisoft@gmail.com> wrote: > >> You have to SIGHUP cron, not restart it. > >> # killall -HUP cron > > > > Isn't crontab(1) supposed to do that, without separate > > intervention? > > From man cron > > > Additionally, cron checks each minute to see if its spool > > directory's modification time (or the modification time on > > /etc/crontab) has changed, and if it has, cron will then > > examine the modification time on all crontabs and reload > > those which have changed. Thus cron need not be restarted > > whenever a crontab file is modified. Note that the > > crontab(1) command updates the modification time of the > > spool directory whenever it changes a crontab. OK, I had the mechanism wrong. The main point is, it should not require manual intervention by an administrator to get cron(8) to notice when crontab(1) has revised a crontab. The one thing I can think of, short of a bug, is that a change made less than 1 minute before the newly-added or -removed event might not be noticed in time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4c81e879.vT3c8HBQCXR5AwE5%perryh>