Date: Fri, 4 Apr 2014 16:13:09 -0400 From: John Baldwin <jhb@freebsd.org> To: Karl Pielorz <kpielorz_lst@tdx.co.uk> Cc: freebsd-hackers@freebsd.org Subject: Re: Stuck CLOSED sockets / sshd / zombies... Message-ID: <201404041613.09808.jhb@freebsd.org> In-Reply-To: <18B08A7E8585B0C4A89A05E6@study64.tdx.co.uk> References: <3FE645E9723756F22EF901AE@Mail-PC.tdx.co.uk> <201404031614.40951.jhb@freebsd.org> <18B08A7E8585B0C4A89A05E6@study64.tdx.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, April 03, 2014 4:54:35 pm Karl Pielorz wrote: > > --On 3 April 2014 16:14:40 -0400 John Baldwin <jhb@freebsd.org> wrote: > > > That's really odd. A single threaded program has no business even trying > > to grab a lock. Is your sshd even linked against libthr via ldd? > > Bearing in mind this system was installed as 10.0-R, 10.0-STABLE checked > out via SVN, and the world built from that... > > Looking at sshd with ldd gives: > > " > # ldd /usr/sbin/sshd > /usr/sbin/sshd: > ... > libthr.so.3 => /lib/libthr.so.3 (0x8038d7000) > " > > So I'm guessing that's a yes? Ugh, ok. Is this easy to reproduce? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201404041613.09808.jhb>