Kill remote in response to client death?
If execute, say, "ssh blue sleep 600", then a ps on blue shows me something
like this:
UID PID PPID C STIME TTY TIME CMD
jhayes 15608 15606 0 15:25:16 ? 0:00 /usr/local/openssh/sbin/sshd
jhayes 15609 15608 1 15:25:16 ? 0:00 tcsh -c sleep 600
jhayes 15621 15609 0 15:25:17 ? 0:00 sleep 600
If I then kill the ssh client, a subsequent ps on blue shows:
UID PID PPID C STIME TTY TIME CMD
jhayes 15609 1 0 15:25:16 ? 0:00 tcsh -c sleep 600
jhayes 15621 15609 0 15:25:17 ? 0:00 sleep 600
So the ssh command creates a hierarchy of three processes on blue, and killing
it only terminates the topmost of the three. I want to purge all three
processes in response to a ^C on the client side. Is there any way to get ssh
to behave this way? A process that writes to stdout/err will generate a
SIGPIPE, but I'd like to kill it even if it produces no output.
Thanks,
Jim Hayes
jhayes@cs.ucsd.edu
Received on Fri Jan 31 12:41:44 2003
This archive was generated by hypermail 2.1.8
: Wed Aug 23 2006 - 14:02:52 EDT
|