Skip to content
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.

Sign up for GitHub

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

Jump to bottom

new kernels are not detected on Debian #88

Open
evgeni opened this issue Jun 18, 2017 · 1 comment
Open

new kernels are not detected on Debian #88

evgeni opened this issue Jun 18, 2017 · 1 comment
Labels
bug distro Anything outside of Fedora effort/high Requires 3 or more days gain/low Affect only one person, corner case, has easy workaround

Comments

@evgeni
Copy link

evgeni commented Jun 18, 2017

ohai, it seems tracer does not detect new kernels on Debian.

the code added in #83 looks for folders in /lib/modules that are newer than the running kernel, but Debian does not increment the kernel version string on every update, thus the folder does not change.
@evgeni
Copy link
Author

evgeni commented Jun 18, 2017

you'd need to actually look inside the on disk and in memory kernels to check that:
see https://github.com/liske/needrestart/blob/master/perl/lib/NeedRestart/Kernel/Linux.pm
or https://github.com/bzed/pkg-nagios-plugins-contrib/blob/master/dsa/checks/dsa-check-running-kernel

@FrostyX FrostyX added bug distro Anything outside of Fedora labels Nov 26, 2023
@FrostyX FrostyX added effort/high Requires 3 or more days gain/low Affect only one person, corner case, has easy workaround labels Jan 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug distro Anything outside of Fedora effort/high Requires 3 or more days gain/low Affect only one person, corner case, has easy workaround
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@evgeni @FrostyX