Re: PROPOSAL to serialize cron.{daily,weekly,monthly}
begin "Artur R. Czechowski" <arturcz@hell.pl> dedi ki:
> On Tue, Sep 07, 2004 at 06:31:35PM +0300, Abdullah Ramazanoglu wrote:
>
>> Here is the problem: Anacron works as a fall back mechanism where cron
>> fails, due to various reasons, to do its job. In a normal 7/24 system
>> anacron never kicks in cron.xxxly batches, as cron does its job
>> successfully. Note that /etc/cron.d/anacron starts anacron at 7:30,
>> whereas cron starts cron.{daily,weekly,monthly} at 6:25, 6:47 and 6:52
>> respectively.
>
> Are you sure? Let's look into /etc/crontab:
> 25 6 * * * root test -x /usr/sbin/anacron || run-parts --report /etc/cron.daily
> then, for legibility, let's separate a command:
> test -x /usr/sbin/anacron || run-parts --report /etc/cron.daily
> and analyze them.
> test -x /usr/sbin/anacron means "/usr/sbin/anacron is runnable for me"
> so, the whole command:
> /usr/sbin/anacron is runnable for me OR execute run-parts.
>
> If you have installed anacron the first part is true and run-parts wont be
> executed. The same for weekly/monthy at 6:47 and 6:52. Then at 7:30 anacron
> shall be run.
Hmm, you're right. Sorry for the confusion. It's been a bit of time to
remember but I guess I must have first installed just cron, and later on
crontab when my serialization fix was already in place for some time,
which bypasses anacron check. Then I've overlooked the fact that anacron
doesn't kick in because of my own changes to crontab.
Well, this defeats 3 legs of my previous case, I guess. Still a leg
remains, however. Namely, syncing the behavior of cron with anacron, so it
would be a more consistent system, regardless of whether anacron is
installed or not.
Thank you for clearing up the issue.
--
Abdullah | aramazan@ |
Ramazanoglu | myrealbox |
________________| D.0.T cöm |__
Reply to: