On 12/10/2014 12:05 PM, Lennart Poettering wrote:
No. At least on Fedora we only have a limited number of system cron

Right less then 45 ( out of 100 in total ) that might have been applicable for migration

and I'd rather see those converted natively, rather than
maintaining a compatibility generator for a longer time

Right arguably upstream should never carry generators of anykind ( and at one point we will need to drop the legacy sysv initscript compatibility otherwise those legacy initscripts will never get migrated and their daemon be fixed either if applicable ) and beside the limitation that timer units suffer from, cron generators can create quite the surprise for administrators, especially on batch servers.

That said out of necessity ( It's easier to write a generator rather then go through the leg work and bureaucracy of dealing with distribution processes ) there has already been written by Dwayne Bent, Konstantin Stepanov, Daniel Schaal and Alexandre Detiste an "systemd-crontab" which includes crontab generator which can be found here [1]

But I urge distribution integrators to go the extra mile and rather migrate existing cron jobs for components that already depend on systemd and or are part of the core/base OS and might thus benefit from that migration.

I would have migrating all the relevant cron jobs in Fedora but I had enough due to certain corporate attitude towards the project, certain part of their employees and their behaviour and as a result of that in the end things turned out differently than I had planned or anticipated.

That work would have most likely covered everything that should have been migrated in Mageia,OpenSuse and Arch ( Debian is of a different Scale ) but you know shit happens and things go unfixed as an result of that.


1. https://github.com/kstep/systemd-crontab-generator
2. https://github.com/systemd-cron/systemd-cron
systemd-devel mailing list

Reply via email to