> If you can't kill a process (even with SIGKILL), it means
> that the process currently can't be put on the run queue,
> because only processes that are able to run can receive
> signals.  Given that, such a situation usually has one of
> these three reasons:

Clearly and I/O block is my specific problem, given the behavior.

That term "signal" in the man page did seem like kill is not the
brute-force method for making a process go away.  Suprising no one has
cooked up something more 'lethal'...

freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to