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
batch mode yields different kernel results as root versus user #246
Comments
You are using a old version of needrestart, can you check if it also happens with a more recent release of needrestart? I was not able to reproduce this issue on Debian stable (needrestart 3.5). |
Yes, I noticed that Ubuntu 18.04 (Bionic) packages are stuck on 3.1. Let me research a bit into how to install the latest release in my environment and I'll test it. In the meantime, I think I have determined that the difference between root and user results is due to /boot/vmlinuz* having 0600 permissions. The script I'll follow up once I can install and test a more recent version |
I was able to straightforwardly update to 3.5 by pulling from ubuntu jammy. I get the same results: user mode indicates that a kernel difference exists whereas root mode does not. The issue appears to be that the kernel files in /boot are not readable by non-root users. It may take a little more work to install 3.6.
|
You have those |
I think it is a bug that it reports an erroneous answer rather than returning an error. |
I'm using needrestart in batch mode in a script which runs in user space. It returns an indication that a restart is needed, but when run as root, it does not. It seems like it should either (1) report the same results whether run as root or not, or (2) report some kind of error to a non-root user if root is required to achieve accurate results.
The system has been rebooted several times while this condition persists. If I am misusing the tool, I would be grateful for redirection to using it correctly. I'll also happily attempt diagnostics on the subject system with direction.
-Galen
The text was updated successfully, but these errors were encountered: