-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
needs-restarting: get systemd boot time from UnitsLoadStartTimestamp #527
needs-restarting: get systemd boot time from UnitsLoadStartTimestamp #527
Conversation
1ed1009
to
eac7a3d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks! Related: rpm-software-management/dnf5#1198
thanks for the review. apparently there is a failing test that need to pass before merging |
eac7a3d
to
bfcd1d2
Compare
I am changing the logged message to debug level since it could be quite annoying and I don't want to change the output of the plugin |
Resolves https://issues.redhat.com/browse/RHEL-35577. Get the boot time from UnitsLoadStartTimestamp if systemd is available, but make sure to use the kernel boot time for calculating process start times using data from procfs. The previous attempt [1] at this failed to do so and introduced a regression [2]. Also, get the kernel boot time from the btime field of /proc/stat instead of calculating it from /proc/uptime, to be consistent with what procps-ng does. [1] rpm-software-management#527 [2] https://issues.redhat.com/browse/RHEL-39775
Resolves https://issues.redhat.com/browse/RHEL-35577. Get the boot time from UnitsLoadStartTimestamp if systemd is available, but make sure to use the kernel boot time for calculating process start times using data from procfs. The previous attempt [1] at this failed to do so and introduced a regression [2]. Also, get the kernel boot time from the btime field of /proc/stat instead of calculating it from /proc/uptime, to be consistent with what procps-ng does. [1] rpm-software-management#527 [2] https://issues.redhat.com/browse/RHEL-39775
Resolves https://issues.redhat.com/browse/RHEL-35577. Get the boot time from UnitsLoadStartTimestamp if systemd is available, but make sure to use the kernel boot time for calculating process start times using data from procfs. The previous attempt [1] at this failed to do so and introduced a regression [2]. Also, get the kernel boot time from the btime field of /proc/stat instead of calculating it from /proc/uptime, to be consistent with what procps-ng does. [1] rpm-software-management#527 [2] https://issues.redhat.com/browse/RHEL-39775
Resolves https://issues.redhat.com/browse/RHEL-35577. Get the boot time from UnitsLoadStartTimestamp if systemd is available, but make sure to use the kernel boot time for calculating process start times using data from procfs. The previous attempt [1] at this failed to do so and introduced a regression [2]. Also, get the kernel boot time from the btime field of /proc/stat instead of calculating it from /proc/uptime, to be consistent with what procps-ng does. [1] rpm-software-management#527 [2] https://issues.redhat.com/browse/RHEL-39775
Resolves https://issues.redhat.com/browse/RHEL-35577. Get the boot time from UnitsLoadStartTimestamp if systemd is available, but make sure to use the kernel boot time for calculating process start times using data from procfs. The previous attempt [1] at this failed to do so and introduced a regression [2]. Also, get the kernel boot time from the btime field of /proc/stat instead of calculating it from /proc/uptime, to be consistent with what procps-ng does. [1] rpm-software-management#527 [2] https://issues.redhat.com/browse/RHEL-39775
Resolves https://issues.redhat.com/browse/RHEL-35577. Get the boot time from UnitsLoadStartTimestamp if systemd is available, but make sure to use the kernel boot time for calculating process start times using data from procfs. The previous attempt [1] at this failed to do so and introduced a regression [2]. Also, get the kernel boot time from the btime field of /proc/stat instead of calculating it from /proc/uptime, to be consistent with what procps-ng does. [1] rpm-software-management#527 [2] https://issues.redhat.com/browse/RHEL-39775
Resolves https://issues.redhat.com/browse/RHEL-35577. Get the boot time from UnitsLoadStartTimestamp if systemd is available, but make sure to use the kernel boot time for calculating process start times using data from procfs. The previous attempt [1] at this failed to do so and introduced a regression [2]. Also, get the kernel boot time from the btime field of /proc/stat instead of calculating it from /proc/uptime, to be consistent with what procps-ng does. [1] #527 [2] https://issues.redhat.com/browse/RHEL-39775
Resolves https://issues.redhat.com/browse/RHEL-35577. Get the boot time from UnitsLoadStartTimestamp if systemd is available, but make sure to use the kernel boot time for calculating process start times using data from procfs. The previous attempt [1] at this failed to do so and introduced a regression [2]. Also, get the kernel boot time from the btime field of /proc/stat instead of calculating it from /proc/uptime, to be consistent with what procps-ng does. [1] rpm-software-management#527 [2] https://issues.redhat.com/browse/RHEL-39775
Resolves https://issues.redhat.com/browse/RHEL-35577. Get the boot time from UnitsLoadStartTimestamp if systemd is available, but make sure to use the kernel boot time for calculating process start times using data from procfs. The previous attempt [1] at this failed to do so and introduced a regression [2]. Also, get the kernel boot time from the btime field of /proc/stat instead of calculating it from /proc/uptime, to be consistent with what procps-ng does. [1] #527 [2] https://issues.redhat.com/browse/RHEL-39775
No description provided.