From owner-freebsd-questions Sun Jan 2 15:15: 8 2000 Delivered-To: freebsd-questions@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 5F76A14D24 for ; Sun, 2 Jan 2000 15:14:42 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.092 #1) id 124sYB-000Lbx-00; Sun, 02 Jan 2000 21:28:31 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.092 #1) id 124sYB-00017r-00; Sun, 02 Jan 2000 21:28:31 +0000 Date: Sun, 2 Jan 2000 21:28:31 +0000 From: Ben Smithurst To: Ryan Thompson Cc: Pekka Savola , freebsd-questions@FreeBSD.ORG Subject: Re: Huge crontab jobs are not run Message-ID: <20000102212831.A4183@strontium.scientia.demon.co.uk> References: <3.0.6.32.20000102140829.008136d0@netcore.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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