Path: utzoo!mnetor!uunet!peregrine!ccicpg!turnkey!jack
From: jack@turnkey.TCC.COM (Jack F. Vogel)
Newsgroups: comp.unix.xenix
Subject: Re: Configuring Xenix for 1200/2400 baud access, uucp log management
Message-ID: <179@turnkey.TCC.COM>
Date: 14 Apr 88 21:15:31 GMT
References: <151@amcad.UUCP> <10387@steinmetz.ge.com>
Reply-To: jack@turnkey.TCC.COM (Jack F. Vogel)
Distribution: na
Organization: Turnkey Computer Consultants, Costa Mesa, CA
Lines: 33

In article <10387@steinmetz.ge.com> davidsen@kbsvax.steinmetz.UUCP (William E. Davidsen Jr) writes:
>
>I think the problem you are seeing is caused by initialization noise as
>the connect is made.
 
No, the problem is not noise, the problem is as a couple of posters have
suggested, without knowing why, the login script.

>	"" "" gin:--gin:-BREAK-gin:--gin:
>    I have no idea why this works better.
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The original posters login script started like this:
	"" BREAK ogin:.......
The reason this causes problems is that it says "expect nothing, send a
break". But this never gives time for getty to get its login prompt out the
port, it then gets "confused" and drops the line. As the original poster
also noticed it happened in both directions, nobody's getty likes to be
interrupted before its had its say :-} :-}. Your modified script, Bill,
has the same effect as saying: ogin:-\b-ogin:.....It gives the getty the
time to put out a prompt and if it's gibberish it sends a break. The
whole question of what direction to cycle the baud rates depends on
convenience for a particular system (i.e., do you have more 2400 or
1200 connections).

					Hope this helps explain,



-- 
Jack F. Vogel
Turnkey Computer Consultants, Costa Mesa, CA
UUCP: ...{nosc|uunet}!turnkey!jack 
Internet: jack@turnkey.TCC.COM