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]

ssh SIGHUP behavior with remote commands

Subject: ssh SIGHUP behavior with remote commands
Date: Mon, 17 Jul 2006 08:51:36 -0700
I use ssh (OpenSSH_4.3p2, OpenSSL 0.9.7j on Gentoo Linux kernel 2.6.15) to run 
a command on a remote machine (same version) that doesn't terminate without 
an explicit kill.  Is it possible to send this signal through ssh without 
using a login shell?  Ideally, I'd be able to run "ssh server command," and 
then send SIGHUP to to the ssh process, which would result in it sending some 
signal to the command.  However, the current behavior is that command is left 
running while ssh terminates.  Alternatively, is it possible to tell ssh to 
send a signal to a command it is running on a remote server?

I searched google and saw that there has been some discussion of similar 
issues in the past, but am not clear how/if it was resolved.  Thanks a lot 
for the help,

Ryan

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