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 s
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
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//exe symlinks. C
Hi Axel,
On 05/01/2014 12:13 PM, Axel Beckert wrote:
The problem is the second scanning pass which looks for the parent
processes. It seems to happen if a process is a child of a kernel
thread... sadly I could not reproduce it, yet.
Strange. I really wonder what's so different on my boxes. Did
severity 746550 wishlist
Hi Thomas,
Thomas Liske wrote:
> > At least all of these pids I checked were kernel threads for which the
> > above behaviour is IIRC normal:
> >
> > # ps auxwww | fgrep --color '['
> > root 1 0.0 0.0 13228 668 ?Ss2013 2:21 init [2]
> > root
Hi Axel,
On 05/01/2014 01:46 AM, Axel Beckert wrote:
>> On 04/29/2014 12:35 PM, Axel Beckert wrote:
>>> # needrestart
>>> Scanning processes...
>>> Scanning candidates.Use of uninitialized value in pattern match (m//) at
>>> /usr/sbin/needrestart line 2
6 matches
Mail list logo
