From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 26 03:16:15 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id DA184106564A for ; Sat, 26 Nov 2011 03:16:15 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 279101519CA; Sat, 26 Nov 2011 03:16:15 +0000 (UTC) Message-ID: <4ED059FE.8090502@FreeBSD.org> Date: Fri, 25 Nov 2011 19:16:14 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111110 Thunderbird/8.0 MIME-Version: 1.0 To: Tim Kientzle References: <201111251609.pAPG97dT008848@slippy.cwsent.com> <4ED011C6.8060605@FreeBSD.org> In-Reply-To: X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: Jason Hellenthal , hackers@freebsd.org Subject: Re: cron(8) mis-feature with @reboot long after system startup X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Nov 2011 03:16:15 -0000 On 11/25/2011 16:16, Tim Kientzle wrote: > > On Nov 25, 2011, at 2:08 PM, Doug Barton wrote: > >> On 11/25/2011 08:09, Cy Schubert wrote: >>> You're right. Sorry. It was late, after a long night of O/T. >> >> Actually I was in the same boat, which is why my reply was even grumpier >> than usual, sorry. >> >> Meanwhile I like your suggestion of having cron check that it's within >> $time_period before running the @reboot jobs > > Hmmm… I thought rc.d distinguished between boot-time > and non-boot-time starts already. Well sure, rc.d does, but /usr/sbin/crond doesn't. > It might be simpler and more accurate to add a crond command-line > option (--run-reboot-scripts) and have the rc.d scripts only pass that > in when crond is started at boot time. No, since that wouldn't help if the user started it without rc.d, and more importantly, the current behavior is broken. :) Doug -- "We could put the whole Internet into a book." "Too practical." Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/