On 09/03/10 09:19, per...@pluto.rain.com wrote:
Chris Rees<utis...@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.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
