Hi!
Ryan Reich wrote:
> On 7/1/07, Daniel Schömer <[EMAIL PROTECTED]> wrote:
>> $ sudo fcrontab -l systab
>> [...]
>> %hourly 0-30 run-parts --report /etc/cron.hourly
>> %daily * * run-parts --report /etc/cron.daily
>> [...]
> Thanks for sharing this. [...] This is a more elegant solution
> than the run-crons method, though it doesn't have quite the
> same effect as instructing cron to actually run each command
> separately (their outputs will be mailed in conglomerate,
> rather than one mail per periodic program. This is, according
> to your preferences, either a bug or a feature.
I have never really thought about the combined mails. I'm using
this on my desktop with only a few scripts in
/etc/cron.{h,d,w,m}*/. Thinking about it now, I would prefer one
mail per script. At least when there are more than just a few
scripts run by cron.
I can't see an elegant way implementing this directly in fcron.
A modified version of run-parts that's capable of mailing the
output of each script (or all in conglomerate if specified) to
the runnig user (or a specified account) may do.
> Less ambiguously a bug, though, is that the syslog will only
> record running run-parts and not which parts were run).
Would it be sufficient to let this also be done by run-parts?
Then there would be records of fcron starting run-parts and
records of run-parts starting each script.
> Have you any thoughts on what to do with check_system_crontabs?
> Its schedule is inherently reactive and not periodic, so
> really, administering it with (f)cron at all is a logical
> error. That's why I suggested inotify in the first place.
I must say, I can't remember that I've seen check_system_crontabs
on my desktop; maybe I just suppressed it :-). Now that I think
of it, I'm remembering an elog message from the fcron ebuild
telling me to use the fcrontab systab for system-wide jobs
instead of /etc/{f,}crontab.
Using inotify sounds more logical for me than using (f)cron for
this.
Daniel Schömer
--
[EMAIL PROTECTED] mailing list
