Arthur Chance free...@qeng-ho.org wrote:
On 09/03/10 09:19, per...@pluto.rain.com wrote:
Chris Reesutis...@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
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?
On 2 Sep 2010 21:11, patrick gibblert...@gmail.com wrote:
I recently upgraded a FreeBSD 7.0 system to 8.1-RELEASE (via
On 09/03/10 09:19, per...@pluto.rain.com wrote:
Chris Reesutis...@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
Yes, it's definitely updating:
[r...@juno /var/cron/tabs]# ls -ald /var/cron/tabs
drwx-- 2 root wheel 512 Sep 2 12:49 /var/cron/tabs
And after editing my crontab:
[r...@juno /var/cron/tabs]# ls -ald /var/cron/tabs
drwx-- 2 root wheel 512 Sep 3 10:25 /var/cron/tabs
I've been
You have to SIGHUP cron, not restart it.
# killall -HUP cron
Chris
Sorry for top-posting, Android won't let me quote, but K-9 can't yet do
threading.
On 2 Sep 2010 21:11, patrick gibblert...@gmail.com wrote:
I recently upgraded a FreeBSD 7.0 system to 8.1-RELEASE (via
