Date: Thu, 03 Apr 2014 20:38:39 +0100 From: Karl Pielorz <kpielorz_lst@tdx.co.uk> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Stuck CLOSED sockets / sshd / zombies... Message-ID: <4B53DEF2407E2EC90A8DDF9D@study64.tdx.co.uk> In-Reply-To: <201404031232.16465.jhb@freebsd.org> References: <3FE645E9723756F22EF901AE@Mail-PC.tdx.co.uk> <201404031103.41171.jhb@freebsd.org> <6F730B3126CC5AE636D1E2A0@Mail-PC.tdx.co.uk> <201404031232.16465.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--On 3 April 2014 12:32:16 -0400 John Baldwin <jhb@freebsd.org> wrote: >> " >> USER CMD PID FD MOUNT INUM MODE SZ|DV R/W >> root sshd 4346 8* local stream fffff80002e55c30 <-> >> fffff80002e552d0 ... >> root sshd 4344 4* local stream fffff80002e552d0 <-> >> fffff80002e55c30 " > > Right, so it's just blocked on a UNIX domain socket from the parent > waiting for the parent to tell it to do something. The root issue is the > parent (as I feared). Is 4344 threaded (procstat -t?) " # procstat -t 4344 PID TID COMM TDNAME CPU PRI STATE WCHAN 4344 100068 sshd - 0 120 sleep urdlck " -Karl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B53DEF2407E2EC90A8DDF9D>