Re: [arch-general] Comment on: Use systemd timers instead of /etc/cron.{hourly, daily, weekly, monthly}?

of files), but it does what I had in mind. Hopefully, as more distros start to migrate away from cron, systemd maintainers will simplify and standardize the configuration needed for cron replacement. Maciej Puzio

Re: [arch-general] Comment on: Use systemd timers instead of /etc/cron.{hourly, daily, weekly, monthly}?

On Tue, May 6, 2014 at 3:13 PM, Leonid Isaev wrote: > On Tue, 6 May 2014 13:23:26 -0500 > Maciej Puzio wrote: > >> As I wrote before, I can edit every timer file and set the elapse >> time. What I can't do is to change one setting which says when daily >> mai

Re: [arch-general] Comment on: Use systemd timers instead of /etc/cron.{hourly, daily, weekly, monthly}?

Thomas Bächler wrote: > Of course you can configure the elapse time, by adjusting the associated > .timer unit. With anacron, there was no way to adjust the time, so this > is a step forward. As I wrote before, I can edit every timer file and set the elapse time. What I can't do is to change one s

Re: [arch-general] Comment on: Use systemd timers instead of /etc/cron.{hourly, daily, weekly, monthly}?

ddition to logrotate/updatedb/man-db/shadow. Thanks Maciej Puzio

Re: [arch-general] Comment on: Use systemd timers instead of /etc/cron.{hourly, daily, weekly, monthly}?

reedesktop.org/show_bug.cgi?id=77938 However, now I started to worry about AccuracySec=12h. Even if systemd maintainers implement a way to customize timer elapse time (as I proposed in RFE), the long period in AccuracySec will then become a problem. Thanks Maciej Puzio

[arch-general] Comment on: Use systemd timers instead of /etc/cron.{hourly, daily, weekly, monthly}?

sure what to suggest as a general fix for this issue, other than a feature request to systemd upstream maintainers. I guess it is too late to roll back the changes in affected Arch packages. I am posting this for other users looking for a solution to this problem. Thanks Maciej Puzio