On 2017-10-29 14:16, Michael Orlitzky wrote:
On 10/29/2017 07:46 AM, Remy Blank wrote:
I attached a patch to the bug, but considering how old the bug is, and
from the tone of the discussion there, I have little hope that it gets
applied. If you would like to see this fixed, it may be worth chiming
in
on the bug. Or if you're a kind Gentoo developer listening to affected
users, to take action.
If only it were that easy. First: vapier is the only member of the cron
project, and he's happy with the way cronbase works.
This shows the lack of maintainers only. Don't wanna start a discussion
about the reasons. IMHO the cronbase ebuild is faulty by design - sorry.
And then the real issue: no one knows what our cronbase is doing, and
it
does whatever it does all wrong -- but some people are probably relying
on it. My proposal was to make cronbase stupider, with something like
9 5 * * * root find /etc/cron.daily -execdir '{}' \;
That says: run everthing in cron.daily[0], every day, at 05:09. It does
exactly that: it has DST issues, if your machine is off the jobs won't
run, etc. But it's predictably stupid and works as advertised, unlike
the run-crons shell script we have now.
Looks a bit like a concept. As I have to work with different OS's I
defined for me:
1. a crontab entry have to call a shell script always, at least a
(minimal) wrapper
2. the shell script have to do some checks, e.g. the last run - I did
wrote a small 'include' script for that
Thus it's portable. The job have to be done once.
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* recommend fcron, it is a bit under estimated. Beside its progressive
design and w/o consulting the man page now again - AFAIR it can handle
DST issues like above through options in fcrontab. But with my concept I
don't need/use it. Be aware that some options could show an unexpected
behavior too - nothing is perfect. Anyhow, by using fcron it is possible
to eliminate the whole cronbase ebuild - it is part of the 20 percent
(round about) which are faulty in Gentoo.
Just an opinion.
[0] In practice, you would want to pass "-type f", "-executable", and
"-maxdepth 1" to the "find" command as well.
--
Sent with eQmail-1.10
