[Bug 1206502] New: Base:System/transactional-update: transactional-update.timer - Persistent attribute of timer is ignored
http://bugzilla.opensuse.org/show_bug.cgi?id=1206502 Bug ID: 1206502 Summary: Base:System/transactional-update: transactional-update.timer - Persistent attribute of timer is ignored Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: reiokorn@tutanota.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- The current RandomizedDelaySec=2h attribute is also applied to every boot, so users who only run their computers for a short time won't get their daily updates reliably. Normally, you'd expect that if the timer isn't run at the time (0:00 + randomized-delay) it will trigger at the next boot. However, this isn't the case at all: This behavior was changed with this merge in systemd https://github.com/systemd/systemd/pull/11608 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206502 http://bugzilla.opensuse.org/show_bug.cgi?id=1206502#c1 --- Comment #1 from B <reiokorn@tutanota.com> --- "With this commit, if the scheduled time of the persistent timer has already elapsed at boot, set the time when systemd first started as the scheduled time and RandomizedDelaySec= is applied to it." https://github.com/systemd/systemd/pull/11608/commits/a87c1d3a979f8c2641471b... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206502 http://bugzilla.opensuse.org/show_bug.cgi?id=1206502#c2 Richard Brown <rbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |rbrown@suse.com Resolution|--- |WORKSFORME --- Comment #2 from Richard Brown <rbrown@suse.com> --- The reported behaviour is _exactly_ how we intend it to be Users do not need every single update snapshot every single time, but need to get it regularly Even though the update is done in the background, it can have a performance impact on CPU/Disk, so running it during/immediately after boot (where CPU/Disk is always used heavily) can cause unwanted disruption from users. So a randomised delay even with persistance is precisely the best balance of ensuring users get their updates, and not being disruptive. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206502 http://bugzilla.opensuse.org/show_bug.cgi?id=1206502#c4 --- Comment #4 from B <reiokorn@tutanota.com> --- (In reply to Thorsten Kukuk from comment #3) (In reply to Richard Brown from comment #2) Ok, thank you for the detailed explanation. I can see where you're coming from and that having it done immediately after boot might become an issue. I'll just adjust it to my specific use case then. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com