It's T for sTopped. "kill -CONT <pid>" will wake it up so it can be killed. Unix is so nice :-), you can't kill things if they're asleep, you have to wake them up before you hit them over the head. If a process gets stuck in "D" (high-priority sleep) you can't wake it up to kill it. Short of hacking the kernel's process table to change the priority which might be easy now there's gdb access -- but I don't recommend doing that.
Ah, I was half there (read the man page over someone's shoulder) - says "traced or stopped".
But I can 'kill -9' any stopped process that I actually stop myself (with 'kill -STOP' or <Ctrl-Z>) without 'kil -CONT', so why was this one different?
-- [neil@xxx ~]# rm -f .signature [neil@xxx ~]# ls -l .signature ls: .signature: No such file or directory [neil@xxx ~]# exit
