Deadlock problems with 'kill PID' on CURRENT
Martin Blapp
mb at imp.ch
Mon Nov 15 09:03:58 PST 2004
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
More information about the freebsd-current
mailing list