Re: PROPOSAL to serialize cron.{daily,weekly,monthly}

[Abdullah Ramazanoglu <ar018@yahoo.com>]

begin  Steve Greenland <steveg@moregruel.net> dedi ki:
> On 08-Sep-04, 15:27 (CDT), Abdullah Ramazanoglu <ar018@yahoo.com> wrote:
>
>> Simply put, I have always found myself in need of running certain
>> procedures at such precise times. I don't know how others manage.
> 
> vi /etc/crontab
> 
> That's what that file is for. The whole "drop a script into a directory"
> mechanism is to support *packages*, so that the local admin can use
> /etc/crontab w/o having to worry.

So I withdraw my proposal. I think it might be a good idea to explicitly
state this somewhere obvious, so that no sysadmin will attempt to use
cron.xxxly for their private maintenance scripts. Perhaps it's already so
and I failed to see it.
 
>> Doesn't my proposal address this issue as well? Anacron and cron
>> doesn't step on each other, cron manages precise timings with
>> serialized batches, while anacron stands-by as the fallback. And its
>> behavior is the same, independent of whether anacron is installed or
>> not. I use it for more than a year and I'm happy with it so far.
> 
> No, it doesn't work that way. If anacron doesn't run the jobs, it's got
> no idea when things have been run. If anacron *is* running the jobs,
> then cron shouldn't.

But even if anacron doesn't run the jobs, /etc/cron.xxxly/0anacron keeps
anacron in sync.

-- 
Abdullah        | aramazan@ |
Ramazanoglu     | myrealbox |
________________| D.0.T cöm |__