On Tue, 29 Jan 2019 at 14:01, Ludwig Nussel
Please don't. But wan't this about boot times? The rpmdb backup is not a boot time service, is it?
It is: [Timer] Persistent=true
Persistent=true has really bad sideeffects, I removed it meanwhile from my timers everywhere.
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 A judgement call has to be made - persistent=true should only be set on timers that absolutely, positively must run as close as possible to the desired time interval. I would argue for anything that can be described as a 'nice to have maintenance cleanup', then "old-fashioned" cron-like behaviour of "if I wasn't booted when I should have run, I'll run it at my regular time next time" is better for many of the things we're talking about here. But, ultimately, for backup-rpmdb, I think it's bonkers we're still running it at all - our default btrfs snapshots take care of that and for anyone who neglects to use that feature, they really should be taking their own backups of /usr/lib/sysimage just as they should of /etc and any user data in /srv or /var they care about. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org