Hello! 26.02.2017 14:48, Mathias Homann пишет:
Am Sonntag, 26. Februar 2017, 07:50:28 CET schrieb 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?
... can systemd timers operate on fixed times, like cron?
'/AccuracySec/=1us'. Example: ================================================ k_mikhail@linux-mk500:~> systemctl cat vba32update.timer # /etc/systemd/system/vba32update.timer [Unit] Description=Runs VBA32 Update Hourly Requires=timers.target [Timer] OnBootSec=2min OnUnitInactiveSec=1h AccuracySec=1us [Install] WantedBy=timers.target ================================================ ================================================ k_mikhail@linux-mk500:~> journalctl -e -u vba32update.service ... Фев 26 12:13:14 linux-mk500 systemd[1]: Started VBA32 Anti-Virus Update Service. Фев 26 13:13:14 linux-mk500 systemd[1]: Starting VBA32 Anti-Virus Update Service ================================================ Do you mean such case? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org