On 26 February 2017 at 08:50, nicholas
it seems we have 2 systems for default timed events - systemd and cron - why? - 2 systems is 2X things to learn, 2X things to monitor, 2X things to go wrong - systemd has a (very) nice interface/overview "systemctl list-timers --all" - from limited experience cron bugs/problems can be quite opaque so why is everything not moved to systemd?
I believe it is simply because systemd has no backward compatibility with the cron files. After searching for a while I've found that such compatibility was proposed [1] and rejected [2]. IMHO the rejection reasoning sounds reasonable but it looks like that the system cron jobs weighted against the user defined cron files (sounds like not counted in the decision). It is hard to change user habits/experience developed by years and the conversion to systemd timers looks like a steep curve for the common users. [1] https://lists.freedesktop.org/archives/systemd-devel/2013-August/012591.html [2] https://lists.freedesktop.org/archives/systemd-devel/2013-September/013120.h... Best Regards, Anton Todorov integrations developer storpool.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org