Date: Fri, 03 Sep 2010 10:37:26 +0100 From: Arthur Chance <freebsd@qeng-ho.org> To: gibblertron@gmail.com, freebsd-questions@freebsd.org Subject: Re: 8.1: Cron ignoring crontab updates Message-ID: <4C80C1D6.2050104@qeng-ho.org> In-Reply-To: <4c80af91.0XK7R1NzplpVQC/a%perryh@pluto.rain.com> References: <AANLkTing=YCBQWYanuKa1NHBcBoCX6Fhyg=zGA%2BebtvA@mail.gmail.com> <AANLkTin0_9g_ngjPbPc69uUmUMU82HerbB5BORCckWkt@mail.gmail.com> <4c80af91.0XK7R1NzplpVQC/a%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. From the original post crontab seems to be working, so all I can suggest is to "ls -ld /var/cron/tabs" before and after using crontab -e and see if the modtime is being changed correctly.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C80C1D6.2050104>