Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!princeton!astrovax!noao!grandi
From: grandi@noao.UUCP (Steve Grandi)
Newsgroups: net.unix-wizards
Subject: Re: getty speed switching under Ultrix v1.2
Message-ID: <490@carina.noao.UUCP>
Date: Fri, 15-Aug-86 12:20:29 EDT
Article-I.D.: carina.490
Posted: Fri Aug 15 12:20:29 1986
Date-Received: Sun, 17-Aug-86 10:26:34 EDT
References: <2996@brl-smoke.ARPA>
Reply-To: grandi@noao.UUCP (Steve Grandi)
Organization: Natl. Optical Astronomy Observatories, Tucson, AZ USA
Lines: 21

In article <2996@brl-smoke.ARPA> iglesias@ICS.UCI.EDU (Mike Iglesias) writes:
>I've set up /etc/gettytab on our Microvax II running Ultrix v1.2 to
>switch line speeds on breaks.  However, it doesn't seem to be very
>reliable.  It appears that Ultrix is seeing one break as several, so
>it skips past the correct speed about half the time.

4.2BSD has an undocumented field in /etc/gettytab called pf.  This
field gives the number of seconds to wait before flushing input at the
login prompt.  When I put a 'pf#1' field in the "rotary" dial-up entries in 
gettytab the similar problems we were having zeroing in on a speed with 
breaks went away; presumably the "pseudo" breaks get flushed before they 
are detected.  Maybe the same field is hiding in Ultrix 1.2?

I have also added a to#180 field to the gettytab entries for our dial-up
lines so that the speed gets reset to "normal" every three minutes.
Our users were getting confused when they called in and found the line
set at 2400 bps; especially upset were those who couldn't send
breaks!
-
Steve Grandi, National Optical Astronomy Observatories, Tucson, AZ, 602-325-9228
{arizona,decvax,hao,ihnp4,seismo}!noao!grandi  grandi%draco@Hamlet.Caltech.Edu