On 01/31/2013 04:23 PM, Bruno Wolff III wrote:
On Thu, Jan 31, 2013 at 10:51:45 -0500,
Bill Nottingham <nott...@redhat.com> wrote:
I would be tempted to say:
"Anything running at a core system level where a dependence on a
separate
cron daemon may be unwanted (or a bad idea) should be migrated, and
nothing
else for now until we have a clearer perspective on the future."
Given that list that would be migration of:
mcelog
mdadm
ovirt-node
prelink (?)
tmpwatch
vdsm-*
But I'm open to other ideas.
I think it will be easier to disable the jobs in systemd without the
next update turning things on. This is useful if you have some package
installed to look at it, but aren't actually running it. Editing the
cron files to turn it off doesn't survive updates, but it should be
possible to do an override in systemd that will survive package updates.
It already does. ( timer units in /etc/systemd/system directory ) in any
case migrating the cron jobs are irrelevant to the feature Lennart
mentioned.
"systemd has supported timer units for activating services based on time
since its inception. However, it only could schedule services based on
monotonic time events (i.e. "every 5 minutes"). With this feature in
place systemd also supports calendar time events (i.e. "every monday
morning 6:00 am", or "at midnight on every 1st, 2nd, 3rd of each month
if that's saturday or sunday")."
I'm the one that has been looking into the benefit from which component
and of which cron job it would be useful for migrating to systemd timer
units and that's totally irrelevant to that feature as I mentioned to
FESCO but given that Bill Notting seems to be butting into that effort
and planning to do it i'll just leave that up to him.
JBG
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
