hang on exit bug under Linux

Nicolas Williams Nicolas.Williams at ubsw.com
Tue Dec 11 06:17:14 EST 2001


Sorry, Unix systems just work this way you know? RSH hangs the same
way if the remote command keeps stdio open. I learned to use rsh with
stdio redirection to /dev/null long before SSH became the norm.

So what's the problem then?

This topic and these arguments seem to be re-tread, over and over.

I'd like to see a client-side option to have the client end the primary
session as soon as the remote command is launched, with an optional
timer. But in the meantime, I know how to redirect stdio. And the
agent/x11/port forwarding hang bug supposedly is fixed (I can't test it
yet), so I'm pretty happy(*).

(*) I'd like a patch that applies cleanly to 2.9p2 for the
agent/x11/port forwarding hang bug. The one I found on the list does
not, in fact, apply.

Cheers,

Nico


On Mon, Dec 10, 2001 at 11:08:13AM -0800, Dan Kaminsky wrote:
> > Hey, I have the same problem to deal with. I deal with it. I always put
> > in explicit stdio redirections to/from /dev/null. What's wrong with that?
> 
> ssh is a general purpose method of running remote commands as if they were
> locally.  Not "specially written remote commands", not "custom apps".  Just
> remote commands.
> 
> That's what it inherited from rsh, and though I perhaps use this
> functionality a bit more...strenuously...then others, I think I have a
> reasonable expectation for dozens of processes to not accumulate.
> 
> I shouldn't have to rewrite applications, or even have to investigate how
> they function in order to run them.  For the most part, ssh is excellent
> about this.  Every once in a while though...and of course, that's the
> problem.  Nothing worse than intermittent failures.
> 
> --Dan
> 
--
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.




More information about the openssh-unix-dev mailing list