Am Sonntag, 29. Oktober 2017, 18:59:31 CET schrieb Ian Zimmerman:
> On 2017-10-29 09:16, Michael Orlitzky wrote:
> > Do you need something smarter? Install anacron, fcron, cronie, or
> > whatever. But the worst thing we can do is try to mimic those
> > intelligent crons and have it fail to do so randomly. That's still
> > your best option, by the way: rewrite your crontab to avoid run-crons,
> > and install a smart cron implementation that does what you want.
> 
> I was glad to find run-crons on gentoo when I migrated from debian,
> which does (and always has done, AFAIR) what you suggest.  The main
> reason was that anacron is also _stupid_: it thinks all months are 30
> days.  If you schedule a monthly job with anacron, it will run on
> January 1st, then on January 31st, then on March 2nd (in most years!)
> etc.  Which may not be too bad when you consider one host by itself,
> but the schedule will get all out of sync with other hosts if they run
> real (non-anacron) monthly cronjobs.
> 
> So, for hosts that are not up 24h per day, anacron is _not_ a full
> solution.  Something like run-crons is needed.  If the gentoo
> implementation is too opaque or buggy, it should be rewritten, not
> discarded.

It's nice that anacron apparently sucks, but what about fcron and cronie?  
I've always wondered why people who need these features don't just one of 
those.  Is there any reason not to?

(FTR: I used fcron for several years before migrating to systemd timers 
specifically because of its support for running missed jobs.)

-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to