I did a little more testing of this problem just now. A SIGKILL does not kill
the process but will lock up the machine. Truss reports the SIGKILL being
continuously sent to the process. If I break into DDB, and then panic, I get a
panic "lockmgr: pid XXX, not exclusive lock holder 0 unlocking".
I didn't have much time for testing, but backing out this change fixes the
problem tail. For some reason, the signal never gets delivered to the process.
The manual page states that the kevent processing is lower priority than signal
handling and that the signal will get processed as normal befor
I am having problems with "tail -f" hanging the machine. I don't know if this
change is related, but I suspect that it might be.
I commonly do a "tail -f" of my log file while doing a buildworld. As soon as I
interrupted the tail, the machine hung. I then tried to figure out what was
causing t
