Date: Fri, 25 Nov 2011 16:16:38 -0800 From: Tim Kientzle <tim@kientzle.com> To: Doug Barton <dougb@freebsd.org> Cc: Jason Hellenthal <jhell@DataIX.net>, hackers@freebsd.org Subject: Re: cron(8) mis-feature with @reboot long after system startup Message-ID: <A3BDEBA2-58E2-4D8D-8F0E-FE020178A131@kientzle.com> In-Reply-To: <4ED011C6.8060605@FreeBSD.org> References: <201111251609.pAPG97dT008848@slippy.cwsent.com> <4ED011C6.8060605@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. >=20 > Actually I was in the same boat, which is why my reply was even = grumpier > than usual, sorry. >=20 > Meanwhile I like your suggestion of having cron check that it's within > $time_period before running the @reboot jobs Hmmm=85 I thought rc.d distinguished between boot-time and non-boot-time starts already. 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. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A3BDEBA2-58E2-4D8D-8F0E-FE020178A131>