From: William Hubbs <williamh@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] rfc: cron.* and modern cron implementations
Date: Sat, 2 Mar 2019 18:05:09 -0600 [thread overview]
Message-ID: <20190303000509.GA31885@linux1.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
All,
someone brought this up on the chat channel today, so I'm bringing it
here to ask for information.
Is there a reason we still use run-parts and the
/etc/cron.{hourly,daily,weekly,monthly} structure to run repeating cron jobs?
From what I read in the chat earlier, it sounds like the modern crons
might be able to handle this without that structure, but I'm not sure.
Thanks,
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2019-03-03 0:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 0:05 William Hubbs [this message]
2019-03-03 0:26 ` [gentoo-dev] rfc: cron.* and modern cron implementations Michael Orlitzky
2019-03-03 0:44 ` Rich Freeman
2019-03-03 1:25 ` Michael Orlitzky
2019-03-03 2:01 ` Rich Freeman
2019-03-03 15:18 ` Michael Orlitzky
2019-03-03 0:27 ` Rich Freeman
2019-03-03 9:26 ` Toralf Förster
2019-03-03 15:00 ` Ralph Seichter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190303000509.GA31885@linux1.home \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox