On 7/26/21 3:42 PM, Eric Schirra wrote:
Am Montag, 26. Juli 2021, 12:02:33 CEST schrieb Danilo Spinella:
On Mon, 2021-07-26 at 11:39 +0200, Carlos E. R. wrote:
On 26/07/2021 11.21, Danilo Spinella wrote:
Any feedback on this change?
openSUSE is moving to systemd timers, AFAIK.
openSUSE will ship systemd timers with the packages but can't remove cronie because a lot of users still use it. For this reason I think it's good to deprecate run-crons and use a well-maintaned program instead.
Complete agreement. I don't use systemd.timers. I don't like systemd.times.
Drawback of systemd timers are that you always have to maintain two files foo.timer and foo.service. And in containers there is most times no systemd (except Kata containers or similar). The advantage is that you have way better control over the timing, e.g. run a script more than once during a minute, or run stuff after time-sync, etc. Another advantage is that like with any other .service you can use systemd's sandboxing service directives for your systemd timer jobs. But still I'd prefer to keep cronie around because many people are used to this very basic service. Ciao, Michael.