[comp.unix.questions] gettytab question ..

jwabik@umn-d-ub.UUCP (08/31/87)

I am having some difficulty configuring /etc/gettytab to deal with 
autobaud for dialups..  I have tried the following two entries in gettytab
with varying amounts of success.  Any help would be appreciated!
My system is a Sun 3/160 running SMI 4.2BSD.

	XXX|Auto-Baud:\
	ab:sp#2400:

The above will NOT allow logins of anything other than 2400 baud.  I've
seen the "ab" (auto-baud) flag set and function on other systems, but it
fails here.

	XXX|D2400|2400-Baud:\
	nx=D1200:sp#2400:

	YYY|D1200|1200-Baud:\
	nx=D300:sp#1200:

	ZZZ|D2400|2400-Baud:\
	nx=D2400:sp#300:

(This is from memory..  Disregard any typos here.. You know what I mean ..)

This entry does the following:

	When I dial in at 2400, works fine.

	When I dial in at 1200, hit RETURN once, gives me 
	a login prompt and will work fine, unless I hit another
	RETURN before I type my login, in which case garbage
	is displayed..  No number of returns will invoke another
	login prompt -- just additional garbage which finally will
	lock everything up..

	When I dial in at 300, hit RETURN twice, gives me a 
	login prompt and will work fine.. If I hit RETURN at
	the login prompt, it begins at 2400 again, and two 
	more returns will give me another 300 baud login 
	prompt, which is exactly what it is supposed to do.

My question is:

	Why, when I dial in at 1200 and hit RETURN at the login prompt
	does the system go into La-la land and never feed me another 
	login prompt, especially when 300 baud works!

	Most of my users will be dialing in at 1200 baud, as well as
	many UUCP'ers, which may decided to send more than one 
	RETURN at carrier detect, thus blowing everything away..


Thanks in advance .. 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Jeff A. Wabik				ARPA:	jwabik@ub.d.umn.edu
University of Minnesota, Duluth		UUCP:	umn-cs!umnd-cs-gw!jwabik
Live long and program.				umn-cs!shamash!jwabik
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

hls@oce-rd1.oce.nl (Harry Schreurs) (09/02/87)

In article <20@umn-d-ub.D.UMN.EDU> jwabik@umn-d-ub.D.UMN.EDU (Jeff Wabik) writes
>I am having some difficulty configuring /etc/gettytab to deal with 
>autobaud for dialups.
>	lock everything up..
>
>My question is:
>
>	Why, when I dial in at 1200 and hit RETURN at the login prompt
>	does the system go into La-la land and never feed me another 
>	login prompt, especially when 300 baud works!
>

Jeff,

You are supposed to hit the "break"-key to switch to another
baud rate!!

Harry Schreurs

/*
 * This note does not necessarily represent the position
 * of Oce-Nederland B.V. Therefore no liability or
 * responsibility for whatever will be accepted.
 */

kai@uicsrd.csrd.uiuc.edu (09/07/87)

I've had the exact same situation occur here, but most people here dialup at
2400 baud, so the few who use 1200 baud have to hangup and redial if they
press return or break too many times.

Both control-c and return work for changing speeds here.

The only reason I can guess for getting stuck at 300 baud is that once the
system tries 300 baud, characters coming in at 1200 or 2400 baud are too short
for the system to recognize them, including return and control-c.


#include <local/standard_disclaimer.h>

Patrick Wolfe                   Internet:  pat@kai.com
System Manager                  UUCP:      {uunet,ihnp4,uiucuxc}!kai.com!pat
Kuck & Associates, Inc.         Arpanet:   pat%kailand@uxc.cso.uiuc.edu
1808 Woodfield Dr.              Bitnet:    pat%kailand@uiucuxc
Savoy, IL  USA  61874           CSnet:     pat%kailand%uxc@uiuc.csnet
Phone:     217-356-2288         Milnet:    pat%kailand@uiucuxc.arpa
Easylink:  6201 1628            Telex:     910 240 9772 (KUCK ASSOC)