how to kill this process?

[Erik Christiansen]

On Thu, May 04, 2006 at 11:02:16AM +0100, Toby Kelsey wrote:
> man 7 signal: "The signals SIGKILL and SIGSTOP cannot be caught, blocked, or
> ignored."

Whoops! Nevertheless, we do seem to be looking at the process being in a
state where it either cannot receive the signal, or cannot give effect
to it. The OP did say the process was using 100% cpu. Even so, the
kernel should preempt at the end of the scheduling interval, and the
signal ought be delivered. Most curious. :-)

Erik