26.02.2017 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?
systemd units need to spend much more time from user to write, than simple 'crontab -e' command. Yes, you can set your tasks in more flexible way via systemd-timers, especially by using AccuracySec= parameter instead of cron-based tasks. So, let both of planning services -- cron and systemd-timers -- will be alive: everyone could use, what is the most convenient for his own planning-tasks. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org