Okay, I got it solved. If you bury stdout and stderr in /dev/null
(rather than have them inherited from the master application), then ssh
will quit normally. Apologies for the noise.
On Nov 8, 2004, at 4:05 PM, Brendan Younger wrote:
On Nov 8, 2004, at 2:52 PM, Tom Pollard wrote:
On Mon, 8 Nov 2004, Brendan Younger wrote:
I'm having problems getting SSH to quit automatically when the
it's executing exits. Specifically, this is what's going on,
1. my application runs a shell script
2. the shell script runs "ssh -q -f user@host command"
3. the shell script exits (ssh and the remote command are still
4. my application exits (ssh session and remote command are still
5. the remote command exits
6. ssh does NOT exit, but just stays open forever until I kill it
How can I get ssh to exit? Running the "ssh -q -f user@host command"
incantation from the command line works as expected, ssh dies after
remote command does.
ssh -n -q -f user@host command
in your shell script. If you don't use '-n' to shut off stdin when
executing a backgrounded ssh command, ssh can hang. (See the ssh man
Unfortunately, that didn't work. Anyone have any other ideas?
Do not post admin requests to the list. They will be ignored.
Scitech mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden