I'm not sure how I got to this point (but see high-level steps below).
I have this zombie process:
root27237 0.0 0.0 0 0 pts/2- Z - 0:00.00 (sh)
Various web resources say "kill the parent" and the zombie child will
die, too. But that's probably not a good idea here,
In Message ,
Paul Goyette wrote:
=>I'm not sure how I got to this point (but see high-level steps below).
=>I have this zombie process:
=>
=>root27237 0.0 0.0 0 0 pts/2- Z - 0:00.00 (sh)
=>
On Thu, 24 Sep 2015, Gary Duzan wrote:
In Message ,
Paul Goyette wrote:
=>I'm not sure how I got to this point (but see high-level steps below).
=>I have this zombie process:
=>
=>root27237 0.0 0.0 0
On Thu, 24 Sep 2015, Greg Troxel wrote:
Paul Goyette writes:
On Thu, 24 Sep 2015, Gary Duzan wrote:
Yup, my zombie's parent PPID==1
If init is really its parent, check its "ps axl" output and
check its WCHAN. If it isn't "wait", maybe run "ktruss -p 1" to
get an
Paul Goyette writes:
> On Thu, 24 Sep 2015, Gary Duzan wrote:
> Yup, my zombie's parent PPID==1
>
>> If init is really its parent, check its "ps axl" output and
>> check its WCHAN. If it isn't "wait", maybe run "ktruss -p 1" to
>> get an idea of what it is doing
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.NetBSD.org, a NetBSD/amd64 host,
using sources from CVS date 2015.09.24.14.58.19.
An extract from the build.sh output follows:
remove_bkpt(phdl, r_debug_state_sym.st_value,
Updating src tree:
P src/distrib/sets/lists/base/md.amd64
P src/distrib/sets/lists/base/shl.mi
P src/distrib/sets/lists/comp/mi
P src/distrib/sets/lists/comp/shl.mi
P src/distrib/sets/lists/debug/md.amd64
P src/distrib/sets/lists/debug/mi
P src/distrib/sets/lists/debug/shl.mi
P