Date: Mon, 15 Nov 2004 18:03:36 +0100 (CET) From: Martin Blapp <mb@imp.ch> To: Peter Wemm <peter@wemm.org> Cc: current@freebsd.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT Message-ID: <20041115180045.B53544@cvs.imp.ch> In-Reply-To: <200411150857.42423.peter@wemm.org> References: <Pine.NEB.3.96L.1041115133457.80435A-100000@fledge.watson.org> <200411150857.42423.peter@wemm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > I had this problem too BTW, but it didn't prevent DDB. Once named or > rndc got stuck, trying to kill them was Really Bad(TM). Both use > libpthread. The programs were stuck in "runnable" state according to > CTRL-T (siginfo). > > No, I haven't looked closer. That system was built about when the last > round of libpthread turmoil was happening. Now if you say it. I had to kill named manually since it has lost his ARGV: Instead of bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 /usr/sbin/named -u bind -t /var/named I just had this at the time the box crashed: bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 [/usr/sbin/named] or bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 [named] after recovery from the crash, now everything is ok again. Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041115180045.B53544>