cron(8) mis-feature with @reboot long after system startup
crees at freebsd.org
Sat Nov 26 11:25:57 UTC 2011
On 26 November 2011 07:25, Doug Barton <dougb at 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?
I find the idea of using time since boot to decide whether this is
startup repellent in the extreme. Whatever solution is decided (and
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?
Plenty of competent coders in here, but please consider me interested in helping
with a solution if needed.
More information about the freebsd-hackers