needs-restarting: get systemd boot time from UnitsLoadStartTimestamp #1198
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For rpm-software-management#1184 Following the reproducers in that issue, UnitsLoadStartTimestamp seems to consistently have the correct boot time even when UserspaceTimestamp is incorrect due to `set-local-rtc 1`. The two times are within a few seconds of each other. I have no idea why UnitsLoadStartTimestamp is correct, maybe systemd reads /etc/adjtime and adjusts the clock after setting UserspaceTimestamp but before setting UnitsLoadStartTimestamp.
|
What does happen if you restart systemd with |
All the timestamps stay the same for me on systemd 253. |
Merged
via the queue into
rpm-software-management:main
with commit Jan 24, 2024
ab1a540
5 of 9 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For #1184
Following the reproducers in that issue,
UnitsLoadStartTimestampseems to consistently have the correct boot time even whenUserspaceTimestampis incorrect due toset-local-rtc 1. The two times are within a few seconds of each other. I have no idea whyUnitsLoadStartTimestampis correct, maybe systemd reads/etc/adjtimeand adjusts the clock after settingUserspaceTimestampbut before settingUnitsLoadStartTimestamp.