Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Closing a process when SSH is interrupted?

Subject: Closing a process when SSH is interrupted?
Date: Mon, 29 Oct 2007 13:19:53 -0500
Hi,

Is there a way to tell SSH that the remote task should be killed once
the client disconnects?

For example, I tried running:

  me@local$ ssh remote sleep 100

And then typed [Ctrl+C] to kill the ssh command on local.  But the
sleep command kept running on remote for the full 100 seconds.  I
think I want to be able to tell the remote machine, "if I interrupt
the ssh client, then kill the process I sent you."

Maybe I should be doing something else.  I'm working on a script that
uses SSH to send some commands to remote machines, but sometimes these
commands can get into infinite loops and need to be killed.  When this
happens, I'd like to be able to have my program kill them.  It seemed
most straightforward to kill the ssh client, but then I discovered
this does not kill the remote process.

Thanks!

Jared

-- 
Jared C. Davis <jared@cs.utexas.edu>
3600 Greystone Drive #604
Austin, TX 78731
http://www.cs.utexas.edu/users/jared/

<Prev in Thread] Current Thread [Next in Thread>