James G. Sack (jim) wrote:
>
> 3) suspend the program with Ctrl-Z (SIGSTOP), then kill %+
> (or %1, or, ..)
When you send a process a SIGSTOP then a SIGTERM, you want to send it a
SIGCONT also so it can process the SIGTERM. Oftimes, this is not
required. You can check the status with jobs at the command line.
Easy ways to give a SIGCONT: fg or bg
> Nestor wrote:
> >I am running htdig and at some point I try to kill the process
> >or control-C and the window does not repond. I am using
> >putty to access a rhel v3.0. I try passing a SIGKILL or SIGTERM
> >from putty's window menu but also nto able to stop the process
> >the only way is to kill the window.
If you do this, ensure the process died by checking the ps(1) or
pstree(1) output. As I understand, closing the window causes the process
to get a SIGHUP. You might want to try a SIGHUP before closing the
window. It seems a bit nicer to me.
> >Is there anything I can do to make sure that the process is kill
> >when I do a 'kill -9 processid'
The process itself never receives the SIGKILL. The kernel handles that.
If there is a blocked I/O, the process will hang around waiting for the
I/O to complete. There is nothing you can do, except to somehow make the
I/O complete. I cannot give further guidance than that.
The only other solution is to reboot. That clears out all outstanding
(and even mediocre ;) I/O connections.
-john
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
