Nicolas.Williams at Nicolas.Williams at
Sat Aug 3 08:14:05 EST 2002

So, this forcefully closes stdout when the session process
leader exits and stderr is already closed?

I'm not sure why that would be a good thing... What am I missing?

The hang-on-exit go around has gone round so many times... -
why buckle now on the position that it's the client's
responsibility to decide to close the SSH connection early
when the session exits, as users expect, and not sshd's?

Why not have an option for the client to do this?



> -----Original Message-----
> From: Markus Friedl [mailto:markus at]
> Sent: Wednesday, July 31, 2002 12:36 PM
> To: openssh-unix-dev at
> Subject: so-called-hang-on-exit
> so, should this go into 3.5?
> Index: serverloop.c
> ===================================================================
> Index: session.c
> ===================================================================

Visit our website at

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