[gentoo-dev] Re: The future of sys-apps/openrc in Gentoo

[Daniel Schömer]

Nikos Chantziaras schrieb:
 On 07/04/2010 05:29 PM, Lars Wendler wrote:
 now that openrc has no active upstram anymore [1] what shall we do?
 How about switching to something that has a very active upstream?
 http://bugs.gentoo.org/150190

I just want to throw in systemd:

http://bugs.gentoo.org/show_bug.cgi?id=318365
http://www.freedesktop.org/wiki/Software/systemd

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

[Daniel Schömer]

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

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

[Daniel Schömer]

Hi!

Ryan Reich wrote:
 [...]
 My issue: I just installed fcron and I have to say, I'm
 a little disappointed with the kludgy mechanism for
 implmenting:

 1. easy configuration, meaning I don't have to run fcrontab
personally

 2. /etc/cron.{hourly,daily,weekly,monthly} These are implmented
by some very silly-looking polling tricks which, even in
principle, will necessarily waste 83% (that's 5/6) of their
efforts and clutter the logs with useless and uninformative
messages.
 [...]

I just want to share my system-wide fcrontab:

  $ sudo fcrontab -l systab
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  !nice(15)
  !noticenotrun(false)
  !serial(true)

  %hourly  0-30  run-parts --report /etc/cron.hourly
  %daily   * *   run-parts --report /etc/cron.daily
  %weekly  * *   run-parts --report /etc/cron.weekly
  %monthly * * * run-parts --report /etc/cron.monthly

I use fcron's capabilities to execute the files in
/etc/cron.{hourly,daily,weekly,monthly}/ once within each period.

Daniel Schömer

-- 
[EMAIL PROTECTED] mailing list