Update timer to be more in-line with dnf-automatic #5183
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This suggestion would update the timer behaviour of
rpm-ostreed-automatic.timer
to be more in line with the behaviour ofdnf-automatic.timer
.Problem Statement
On a laptop which spends a lot of time in sleep mode, the timer frequency used by
rpm-ostreed-automatic.timer
is so infrequent that the service rarely ends up running.To solve this, we can add
Persistent=true
This brings the behaviour into line with how
dnf-automatic.timer
works:https://github.com/rpm-software-management/dnf/blob/69d1f641cda28fc543846524d15ec7291baf3e5a/etc/systemd/dnf-automatic.timer#L10
Just adding this alone can cause issues in environments with slow network bring-up, so we can also add:
Wants=network-online.target
Which also matches the
dnf-automatic.timer
behaviour:I've also added:
After=network-online.target
as a suggestion here, as the systemd docs suggest this might be more robust than just using Wants=.