From owner-freebsd-questions@FreeBSD.ORG Fri Sep 3 09:37:28 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96F37106573A for ; Fri, 3 Sep 2010 09:37:28 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from blue.qeng-ho.org (blue.qeng-ho.org [217.155.128.241]) by mx1.freebsd.org (Postfix) with ESMTP id 23E708FC18 for ; Fri, 3 Sep 2010 09:37:27 +0000 (UTC) Received: from fileserver.home.qeng-ho.org (localhost [127.0.0.1]) by fileserver.home.qeng-ho.org (8.14.3/8.14.3) with ESMTP id o839bQq5052514; Fri, 3 Sep 2010 10:37:26 +0100 (BST) (envelope-from freebsd@qeng-ho.org) Message-ID: <4C80C1D6.2050104@qeng-ho.org> Date: Fri, 03 Sep 2010 10:37:26 +0100 From: Arthur Chance User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.11) Gecko/20100727 Thunderbird/3.0.6 MIME-Version: 1.0 To: gibblertron@gmail.com, freebsd-questions@freebsd.org References: <4c80af91.0XK7R1NzplpVQC/a%perryh@pluto.rain.com> In-Reply-To: <4c80af91.0XK7R1NzplpVQC/a%perryh@pluto.rain.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: 8.1: Cron ignoring crontab updates X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 09:37:28 -0000 On 09/03/10 09:19, perryh@pluto.rain.com wrote: > Chris Rees 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.