so-called-hang-on-exit

[Nicolas.Williams at ubsw.com]

Perfect. Good patch then. Indeed, I had not read the patch.

Question: what happens to the background process groups? what
should happen to them?

By closing the pty master you cause them to get errors when
they next try to interact with the pty slave. Shouldn't they
get SIGHUP? Sshd cannot figure out what the process groups
are, so it can't send them SIGHUP; but an external script
could use the proc tools/ps/lsof to find all those orphaned
process groups and HUP them.

Traditionally you need nohup(1) to start background jobs which
should survive sessions...

Cheers,

Nico
-- 

> -----Original Message-----
> From: Jani Jaakkola [mailto:jjaakkol at cs.Helsinki.FI]
> Sent: Wednesday, August 07, 2002 4:26 PM
> To: Williams, Nicolas
> Cc: fcusack at fcusack.com; openssh-unix-dev at mindrot.org
> Subject: RE: so-called-hang-on-exit
> 

[...] 

> I did not implement any such thing. Read the patch.
> 
> My second patch has no timeouts at all, but it provides 
> almost exactly the 
> same behaviour as the first.

[...] 

> That was exactly what I did.

[...]

> You did not read the patch. I was doing the former.
> 
> As I already said, the fact that the in the first patch was 
> something else 
> that 0ms was because I had to work around some historical code in the 
> openssh select loop, which was not written by me. I would be 
> happy to fix 
> it though, and probably will provide a patch for it 
> (IdleTimeout will need 
> it).

[...]

> I agree with all this.
> 
> - Jani
> 
> 
> 

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.