Date: Fri, 25 Nov 2011 19:16:14 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Tim Kientzle <tim@kientzle.com> Cc: Jason Hellenthal <jhell@DataIX.net>, hackers@freebsd.org Subject: Re: cron(8) mis-feature with @reboot long after system startup Message-ID: <4ED059FE.8090502@FreeBSD.org> In-Reply-To: <A3BDEBA2-58E2-4D8D-8F0E-FE020178A131@kientzle.com> References: <201111251609.pAPG97dT008848@slippy.cwsent.com> <4ED011C6.8060605@FreeBSD.org> <A3BDEBA2-58E2-4D8D-8F0E-FE020178A131@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ED059FE.8090502>