Xref: utzoo comp.dcom.modems:1426 comp.sys.att:2530
Path: utzoo!mnetor!uunet!husc6!yale!cmcl2!nrl-cmf!mailrus!ames!elroy!jane!stevo
From: stevo@jane.Jpl.Nasa.Gov (Steve Groom)
Newsgroups: comp.dcom.modems,comp.sys.att
Subject: Re: Has anyone gotten a Trailblazer working on tty000 (UNIXPC)
Message-ID: <5434@elroy.Jpl.Nasa.Gov>
Date: 11 Feb 88 23:23:58 GMT
References: <241@icus.UUCP> <40@tarkus.UUCP>
Sender: news@elroy.Jpl.Nasa.Gov
Reply-To: stevo@jane.jpl.nasa.gov (Steve Groom)
Organization: Image Analysis Systems Grp, JPL
Lines: 20
Keywords: Trailblazer, modems, UNIXPC, 3B1, tty000, tty001, 4024

In article <40@tarkus.UUCP> jcs@tarkus.UUCP (John C. Sucilla) writes:
>....There is still one problem
>with this configuration though, when a remote user dials in and gets
>blown off the machine for some reason the users shell never terminates
>even though CD went away. If they logoff normally uugetty launches again
>as expected.

I had this problem with a Sun 2/170. When the 'Blazer disconnects, it
holds DSR off for some period (specified by S47).  If that period
isn't long enough for the host to see it drop, then the host doesn't know
that the connection is gone. The default setting for S47 is 4 (=200ms), I set
it at 40 (2 sec) and the host started seeing the disconnect. Maybe that's
overdoing it a bit, but it worked...

-steve

/* Steve Groom, MS 168-522, Jet Propulsion Laboratory, Pasadena, CA 91109
 * Internet: stevo@elroy.jpl.nasa.gov   UUCP: {ames,cit-vax}!elroy!stevo
 * Disclaimer: (thick German accent) "I know noothingg! Noothingg!"
 */