Date: Sun, 2 Jan 2000 21:28:31 +0000 From: Ben Smithurst <ben@scientia.demon.co.uk> To: Ryan Thompson <freebsd@sasknow.com> Cc: Pekka Savola <Pekka.Savola@netcore.fi>, freebsd-questions@FreeBSD.ORG Subject: Re: Huge crontab jobs are not run Message-ID: <20000102212831.A4183@strontium.scientia.demon.co.uk> In-Reply-To: <Pine.BSF.4.10.10001021443080.33656-100000@sasknow.com> References: <3.0.6.32.20000102140829.008136d0@netcore.home> <Pine.BSF.4.10.10001021443080.33656-100000@sasknow.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ryan Thompson wrote:
> Did you kill -HUP cron? If you didn't do this (or reboot the system),
> your job won't run.
According to the manpage, you don't need to:
| Additionally, cron checks each minute to see if its spool directory's
| modtime (or the modtime on /etc/crontab) has changed, and if it has, cron
| will then examine the modtime on all crontabs and reload those which have
| changed. Thus cron need not be restarted whenever a crontab file is mod-
| ified. Note that the crontab(1) command updates the modtime of the spool
| directory whenever it changes a crontab.
The manpage may be wrong, of course.
--
Ben Smithurst | PGP: 0x99392F7D
ben@scientia.demon.co.uk | key available from keyservers and
| ben+pgp@scientia.demon.co.uk
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000102212831.A4183>