On Tue, 29 Jan 2019 at 17:23, Jan Engelhardt
On Tuesday 2019-01-29 14:32, Richard Brown wrote:
Well, not everywhere as backup-rpmdb.timer still has it :-) Mind catching up on it? Are there any other side effects besides firing at system boot?
If you have a number of persistent timers and they all didn't run at their regular assigned times, then your boot suddenly has ALL of them running at that boot
The combined impact of stuff like btrfs-balance, fstrim, and backup-rpm DB all running at once can be very painful for many machines
Sounds like a design flaw. systemd ought to have an option to run belated timers in sequence. Or perhaps all timers in a certain "group". I still remember the days when (unprivileged) users of a classic multi-user server, able via `crontab -e`, all started their nightly stuff at the same time at 02:00.
https://www.freedesktop.org/software/systemd/man/systemd.timer.html RandomizedDelaySec= can be a help for that problem But I'm reasonably confident that persistent= doesn't honour it..after all, the whole point of Persistent= is "you missed your scheduled run, I'll run it now!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org