ssh SIGHUP behavior with remote commands

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

Relevant Pages

  • Re: ssh SIGHUP behavior with remote commands
    ... a command on a remote machine that doesn't terminate without ... Is it possible to send this signal through ssh without ... it had no logic for dealing with signals it received via the SSH protocol. ...
    (SSH)
  • Re: Ssh/Rsh problems
    ... > I am encountering problems with both ssh and rsh, ... > When I attempt to run a command on a remote machine via ssh, ...
    (comp.os.linux.security)
  • Re: Really need help on this one
    ... Is there a way to read the output of a particular command into ... Heres a better example using ssh. ... set timeout $timeout ... exec kill -9 $pid ...
    (comp.lang.tcl)
  • problem about executing a command without remote shell
    ... I want to execute a command on the remote machine with ssh client, ... But if I first login into the remote machine and then execute the same ...
    (comp.security.ssh)
  • Using SSH to terminate remote systems for disaster recovery
    ... I have a need to terminate a number of AIX 5.1 systems ... from a single script. ... I can do this using ssh. ... if I issue the shutdown command from ssh, ...
    (AIX-L)