http://bugzilla.suse.com/show_bug.cgi?id=913421 Thomas Blume changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume@suse.com Flags|needinfo?(systemd-maintaine | |rs@suse.de) | --- Comment #9 from Thomas Blume --- (In reply to Dirk Weber from comment #8)

...

We can use something similar to your solution from comment 1. it works fine for me for months.

Yes, you should use monotonic timers in order to make systemd respecting the machine state (up or down). Otherwise they will just be triggered by the wallclock and if the system is down at this time they won't get startet. You can find more details about monotonic timers in the systemd.timer manpage at the start of the Options section. Concerning the question in comment#5, logrotate.service is statically enabled. This means it doesn't have an explicit [Install] section and therefore cannot be enabled manually (or via presets). It should be exclusively started by a timer unit. Is logrotate correctly startet when you are using monotonic timers in the logrotate.timer unit? -- You are receiving this mail because: You are on the CC list for the bug.