From owner-freebsd-questions@FreeBSD.ORG Fri Sep 3 17:27:25 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 00ACD10656B0 for ; Fri, 3 Sep 2010 17:27:25 +0000 (UTC) (envelope-from gibblertron@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id A43B78FC15 for ; Fri, 3 Sep 2010 17:27:24 +0000 (UTC) Received: by qwg5 with SMTP id 5so2160972qwg.13 for ; Fri, 03 Sep 2010 10:27:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=tkloA6Xrtv4V3eFEprKKLoIr2AHmHkmYD5lP2VzNvF4=; b=XW1SuKr/NYWgtNaAgLgv6j9bm5voB6HPd/n2PYLjB87DZjfnfPeM+3FD9K659sC9Mi OyIchE15/ekpDW3MqQGM4gsiz/9422Pi9SEXZgSPTy6gIWdPo4Nt8/vOccS5C4G6bcDX p1GR6WbmtpUf309z/3Hn1OhcIK4oboRK5Lsy0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=sDok3zgZZOCOUHBRP/Sv/qfEILwmjHLkjEDYFyGmmMfM9veX5njQze0rO4nVCEgShy 4JE2q5pzdJLsDWJyFET44cx+Ko9QQgQF4RZLpzpJq00jXTsz1QchOzWNU232aLx7TcwK 56Qz/kgP/ih1Sat2AvAvKXBzQm5VZkCA4jg/k= MIME-Version: 1.0 Received: by 10.224.104.4 with SMTP id m4mr216142qao.76.1283534843542; Fri, 03 Sep 2010 10:27:23 -0700 (PDT) Received: by 10.224.20.74 with HTTP; Fri, 3 Sep 2010 10:27:23 -0700 (PDT) In-Reply-To: <4C80C1D6.2050104@qeng-ho.org> References: <4c80af91.0XK7R1NzplpVQC/a%perryh@pluto.rain.com> <4C80C1D6.2050104@qeng-ho.org> Date: Fri, 3 Sep 2010 10:27:23 -0700 Message-ID: From: patrick To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 17:27:25 -0000 Yes, it's definitely updating: [root@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: [root@juno /var/cron/tabs]# ls -ald /var/cron/tabs drwx------ 2 root wheel 512 Sep 3 10:25 /var/cron/tabs I've been using FreeBSD since version 4, and this has never once been an issue, nor is this an issue on a system with a fresh install of 8.1. Patrick On Fri, Sep 3, 2010 at 2:37 AM, Arthur Chance wrote: > On 09/03/10 09:19, perryh@pluto.rain.com wrote: >> >> Chris Rees =A0wrote: >> >>> 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 > >> =A0 =A0 Additionally, cron checks each minute to see if its spool direct= ory's >> =A0 =A0 modification time (or the modification time on /etc/crontab) has >> changed, >> =A0 =A0 and if it has, cron will then examine the modification time on a= ll >> =A0 =A0 crontabs and reload those which have changed. =A0Thus cron need = not be >> =A0 =A0 restarted whenever a crontab file is modified. =A0Note that the >> crontab(1) >> =A0 =A0 command updates the modification time of the spool directory whe= never >> it >> =A0 =A0 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. >