| 1 |
Am Sonntag, 29. Oktober 2017, 18:59:31 CET schrieb Ian Zimmerman: |
| 2 |
> On 2017-10-29 09:16, Michael Orlitzky wrote: |
| 3 |
> > Do you need something smarter? Install anacron, fcron, cronie, or |
| 4 |
> > whatever. But the worst thing we can do is try to mimic those |
| 5 |
> > intelligent crons and have it fail to do so randomly. That's still |
| 6 |
> > your best option, by the way: rewrite your crontab to avoid run-crons, |
| 7 |
> > and install a smart cron implementation that does what you want. |
| 8 |
> |
| 9 |
> I was glad to find run-crons on gentoo when I migrated from debian, |
| 10 |
> which does (and always has done, AFAIR) what you suggest. The main |
| 11 |
> reason was that anacron is also _stupid_: it thinks all months are 30 |
| 12 |
> days. If you schedule a monthly job with anacron, it will run on |
| 13 |
> January 1st, then on January 31st, then on March 2nd (in most years!) |
| 14 |
> etc. Which may not be too bad when you consider one host by itself, |
| 15 |
> but the schedule will get all out of sync with other hosts if they run |
| 16 |
> real (non-anacron) monthly cronjobs. |
| 17 |
> |
| 18 |
> So, for hosts that are not up 24h per day, anacron is _not_ a full |
| 19 |
> solution. Something like run-crons is needed. If the gentoo |
| 20 |
> implementation is too opaque or buggy, it should be rewritten, not |
| 21 |
> discarded. |
| 22 |
|
| 23 |
It's nice that anacron apparently sucks, but what about fcron and cronie? |
| 24 |
I've always wondered why people who need these features don't just one of |
| 25 |
those. Is there any reason not to? |
| 26 |
|
| 27 |
(FTR: I used fcron for several years before migrating to systemd timers |
| 28 |
specifically because of its support for running missed jobs.) |
| 29 |
|
| 30 |
-- |
| 31 |
Marc Joliet |
| 32 |
-- |
| 33 |
"People who think they know everything really annoy those of us who know we |
| 34 |
don't" - Bjarne Stroustrup |
Archives