Date: Sat, 26 Nov 2011 10:54:29 +0000 From: Chris Rees <crees@freebsd.org> To: Doug Barton <dougb@freebsd.org> Cc: Tom Evans <tevans.uk@googlemail.com>, hackers@freebsd.org Subject: Re: cron(8) mis-feature with @reboot long after system startup Message-ID: <CADLo83867HEyraqzS6%2BPcyb=sTnVPP1MRZtiCVYvzcQJGDqZ-g@mail.gmail.com> In-Reply-To: <4ED0944E.7020709@FreeBSD.org> References: <201111260708.pAQ78wvO045883@slippy.cwsent.com> <4ED0944E.7020709@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26 November 2011 07:25, Doug Barton <dougb@freebsd.org> wrote: > On 11/25/2011 23:08, Cy Schubert wrote: >> If average users really do need to run something at boot they're likely >> running some kind of service > > I don't think second-guessing what users are doing is going to be a > useful exercise here. I will also tell you flat out that this is not the > only use for an @reboot cron job. > > Rather than debating whether users *should* be doing it this way or not, > can we please focus on fixing it to be non-stupid? +1 <hat class="armchair-general"> I find the idea of using time since boot to decide whether this is cron's first startup repellent in the extreme. Whatever solution is decided (and I'm thinking a variable passed to rc.d/cron or a state file in /var/run would both work fine), PLEASE let's not go down the route of that. How long? What if I need to restart cron shortly after boot? What if boot takes longer? </hat> Plenty of competent coders in here, but please consider me interested in helping with a solution if needed. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo83867HEyraqzS6%2BPcyb=sTnVPP1MRZtiCVYvzcQJGDqZ-g>