Re: ssh SIGHUP behavior with remote commands
On Mon, 17 Jul 2006, Ryan Olf wrote:
> 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,[/color]
I can give you some vague answers, centered around "you can't".
I investigated OpenSSH's sshd a while back (maybe 4.1 or late 3.x) and
it had no logic for dealing with signals it received via the SSH protocol.
Too bad. I did some work on adding that code, but didn't finish it.
We produce an SSH client for Windows. My goal was to be able to send
signals, especially a SIGHUP that could act as a "conditional
termination", instead of blindly quitting the client side. If the client
sent SIGHUP, and the host software was at a point where it could quit
cleanly, it would respond to the signal by logging out. OTOH, if it was in
a critical point, it could block that signal and not respond to it.
Properly executed, this combination could prevent orphan processes and
I'd be interested in hearing from anyone who has done similar work.
.....Bob Rasmussen, President, Rasmussen Software, Inc.
personal e-mail: [email]email@example.com[/email]
company e-mail: [email]firstname.lastname@example.org[/email]
voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
fax: (US) 503-624-0760