Date: Fri, 19 Sep 2008 13:56:56 -0700 From: "Steve Franks" <stevefranks@ieee.org> To: freebsd-questions@freebsd.org, stevefranks@ieee.org Subject: Re: kill -KILL fails to kill process Message-ID: <539c60b90809191356q5b953b20l7d65e45dcff5033e@mail.gmail.com> In-Reply-To: <200809191812.m8JICBhB011472@lurza.secnetix.de> References: <539c60b90809191041p2490130exa024b1f84d44b2f3@mail.gmail.com> <200809191812.m8JICBhB011472@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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'... Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?539c60b90809191356q5b953b20l7d65e45dcff5033e>