hang on exit - bug or no bug?

[David Terrell]

On Fri, Oct 05, 2001 at 01:07:09PM -0500, mouring at etoh.eviladmin.org wrote:
> 
> 
> On Fri, 5 Oct 2001, Nicolas Williams wrote:
> 
> > On Fri, Oct 05, 2001 at 12:58:37PM -0500, mouring at etoh.eviladmin.org wrote:
> > >
> > > [..]
> > > > >  - write a separate script for checking that the batch job is doing ok
> > > > >  - use intr (yes, Solaris doesn't have one -- write one yourself) on the
> > > > >    client side to set a timeout after which to kill ssh
> > > > >  - write an intr-like command for the remote side that closes the fds
> > > > >    after a timeout and which might be used like so:
> > > > >
> > > > >    ssh -n somehost somecommand 2\>\&1 \| iointr -t 30
> > > > >  - fix the scripts
> > > >
> > > > - fix the daemons
> > > >
> > >
> > > Finxing daemons will solve part of the problem.. but will not solve the
> > > case when you do:
> > >
> > > ssh site.com
> > > vi file
> > > ctrl-z
> > > <wander around>
> > > exit
> > > ..[hang]
> >
> > My shell usually tells me that I have suspended jobs and aborts the
> > exit.
> >
> 
> First time.. But how many people have you seen in a hurry to leave for
> the day go 'Ctrl-D, Ctrl-D'  and ignore the suspended jobs because they
> are use to telnet killing the processes or they die due to lack of std*
> contact.
> 
> I'll admit I've done it a few times.. Not normally under SSH.

This should handled by a sighup to the pgrp, right?

-- 
David Terrell             | "Americans need to watch what they say,
Prime Minister, Nebcorp   | watch what they do, and this is not a
dbt at meat.net              | time for remarks like that; there never
http://wwn.nebcorp.com/   | is." - Ari Fleischer, White House Press Secretary