tags 746363 fixed-upstream
thanks

On 05/06/2014 09:50 PM, Thomas Liske wrote:
Re,

On 05/05/2014 11:38 PM, Axel Beckert wrote:
Hi Thomas,

Thomas Liske wrote:
Does the system has any enhanced security mechanism established?

At least not on purpose. Default debian kernels.

I've attached a small debug script (modified needrestart script)
which analysis the processes and looks for non-readable
/proc/<pid>/exe symlinks. Could you please run it once and provide
it's output?

Will send the whole output to you by private e-mail. Just so far in
advance:

_All_ processes output by the script in detail (i.e. those shown with
"| fgrep cmndline") seem running inside a GNU Screen session. And if
I'm not mistaken, _all_ processes which are running inside a GNU
Screen session are in the detailed output.

So there seems to be some relation between where you suspect the error
and processes running in GNU Screen sessions.

I've found the source of this regression: I'd switched to use
Proc::ProcessTable to parse /proc/<pid> in 0.8. Needrestart requires to
differ between bad links as triggered by kernel processes and symlinks
containing a '(deleted)' target prefix/suffix as triggered by removed
binaries. Proc::ProcessTable hides this difference... as a result any
upgraded binary is never considered to be restarted (as it is detected
to be a kernel process).


HTH,
Thomas



--

    ::  WWW:                         http://fiasko-nw.net/~thomas/  ::
   :::  Jabber:                   xmpp:tho...@jabber.fiasko-nw.net  :::
    ::  flickr:              http://www.flickr.com/photos/laugufe/  ::


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to