Thomas Liske
Thomas Liske
It looks like there is a serious problem with the kernel's proc filesystem entries: - a) - `/proc/$PID/stat` - the starttime (22) is the process start time expressed in seconds...
You are right - my previous argumentation would explain why it does not detect pending interpreter restarts __inside__ of a container (due the calculated process starttime is later than it...
differ if microcode can not be checked due to missing components or unsupported plattform (i.e. ARM)
Yes there is no implementation for ARM.
differ if microcode can not be checked due to missing components or unsupported plattform (i.e. ARM)
I'll keep this as a wishlist issue. The current implementation lacks the ability to differ why microcode checks are not possible.
I assume this false positive is triggered if postfix is run with chroot enabled. Could you please provide the output of `stat /proc/3010/root/usr/lib/postfix/sbin/pickup` - it doesn't exist, doesn't it?
This is weirrd. The "$pid using non-existing $path" message is generated if /proc/$pid/map_files/$maddr nor /proc/$pid/root/$path does exist. But `/proc/11904/root//usr/lib/postfix/sbin/master` seems to exist in your example. Could you give needrestart from...
> So, a workaround is to set `$nrconf{skip_mapfiles} = 1;` but I don't known what's the implications. Should be OK on *GNU/Linux* since `/proc/$PID/maps` seems to be almost reliable.
All modes for skip_mapfiles are just heuristic howto detect obsolete mappings: `0` - works well for classic daemons without chroot/namespaces, for Linux and *BSD `-1` - needrestart ignores if no...
You are using a very old version of needrestart and it looks like a false positive. I would expect that a more recent version of needrestart shouldn't have this issue.
I don't know Ubuntu, maybe you should ask the Ubuntu community for Ubuntu related issues.