Re: [gentoo-dev] Re: Re: Inotify and (f)crontabs

[Ryan Reich]

On 7/1/07, Daniel Schömer <daniel.schoemer@×××.net> wrote:
> Hi!
>
> Ryan Reich wrote:
> >  On 7/1/07, Daniel Schömer <daniel.schoemer@×××.net> wrote:
> >> $ sudo fcrontab -l systab
> >> [...]
> >> %hourly  0-30  run-parts --report /etc/cron.hourly
> >> %daily   * *   run-parts --report /etc/cron.daily
> >> [...]

> > 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.

That works of course, though if you're at the point of modifying
run-parts you might as well modify the crontabs setup.  I mean, having
run-parts do the logging is silly since fcron already has a logging
capability, and since the only point of using run-parts is to assist
fcron.  Otherwise you're just creating further unnecessary complexity.

> > 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.

If there's interest in incorporating this, I wouldn't mind testing my
idea.  Once I get past the initial resistance to doing anything at
all, it's probably two minutes' compilation time plus two more writing
the config files to set up.

-- 
Ryan Reich
-- 
gentoo-dev@g.o mailing list