On 03/04/2014 02:54 PM, Miloslav Trmač wrote:
2014-03-04 15:32 GMT+01:00 Jaroslav Reznik <jreznik(a)redhat.com
= Proposed System Wide Change: cron to systemd time units =
I'm not so sure this should be a system wide change since the migration
it self affects less then half of total shipped cron jobs and for those
that arent it only updates the components specfile to current packaging
== Scope ==
(Everyone), please keep the explicit "Proposal owners"/"other
developers"/"release engineering"/"policies and guidelines"
Other contributors /need/ to know what they are being asked to do by
Accept patches that's what I'm "asking" of them.
* Policies and guidelines:
** Adjust packaging guidelines to mention migration of cron jobs
units for packages that already depend on systemd
Last time this was discussed in
, there were concerns about "confusion of users/admins", specifically
referring to the disabling a .service / disabling a .socket duality.
So we will need packaging guidelines not only for the migration, but
for the timer units themselves.
Not following here we already have packaging guidelines for systemd units
(From the Change page:)
Administrators will have better time trigger in units compared to
cron jobs like for example when administrator stops a
service/daemon the timer unit will stop as well etc.
This would also seem to require detailed packaging guidelines for the
* Fix spec files in packages that are not applicable for migration
Dependency Tracking Bug 2]
* Review and migrate if applicable cron jobs shipped in packages
depend on systemd [Timer Migration Tracking Bug 3]
How many packages (at least an of magnitude) are we talking about? Is
it the 16+3 that are currently blocking the tracker bugs?
To be clear not all cron jobs will be migrate, things like the drupal
cron job "wget -O - -q -t 1 http://www.example.com/cron.php"
migrated since drupal does not depend on systemd and thus has no
business being migrated but "mailman" cron job will be migrated since
mailman ships a daemon hence unit and already depends on systemd so
components that are applicable for migration due to their existing
dependency on systemd are....
For the above components cron jobs will be manually inspected each and
everyone *before* being decided if it will be migrated.