On Saturday 19 January 2002 10:52 am, dman wrote: [snip] > > Those processes are blocked on IO or something. Thus it is the > _kernel_ itself that is stuck, which is why SIGKILL has no effect. > When a process is executing in its own space, the kernel can kill it > and clean up the pieces. When the process is executing inside the > kernel (in a system call) then the kernel can't blow it away because > it would then need to somehow put itself back together. > > -D
i'm totally just guessing here, as i don't use gpg, but wouldn't it be invoked as a child process to whatever mail app is running, and, if that assumption is true, wouldn't the parent process keep it alive?
