Bugzilla – Bug 1115435
atop: migrate from cron to systemd timers
Last modified: 2021-07-12 10:27:24 UTC
This bug is part of TRACKERBUG bug#1115430.
Based on fate#323635 (Reduce usage of cron package in favor of systemd timers) we would like to minimize the number of packages that use cron in favour of systemd timers.
It seems that your package uses cron. Please take a look at it and evaluate if it's possible to migrate your package to use systemd timers without impacting behaviour. If it's not possible, please write down the reason.
Please note that by default, services are not enabled when the package is installed. You probably want your service to be enabled by default so you should create a submit request on systemd-presets-branding-openSUSE package, modifying default-openSUSE.preset file by adding "enable your_service_name.service".
(In reply to Kristyna Streitova from comment #0)
> ... modifying default-openSUSE.preset file by adding "enable
A small correction: it should be "enable your_timer.timer" of course. See  for more information about systemd timers packaging. Feel free to enhance this wiki page. Thanks!
Hello, this is just a friendly reminder that atop hasn't been migrated to systemd timers yet. Can you please take a look at it? Thank you!
Latest version in TW (2.6.0) is already installing service files and timers. However, it is not enabled by default and I think this is the correct behaviour for atop.