Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!csus.edu!ucdavis!csusac!usenet
From: severyn@athena.ecs.csus.edu (Niles Severyn)
Newsgroups: comp.sys.next
Subject: Re: 2.0 getty bug?
Message-ID: <1991May15.212757.4731@csusac.csus.edu>
Date: 15 May 91 21:27:57 GMT
References: <52694@nigel.ee.udel.edu> <1991May6.205949.8240@shaman.com>
Sender: usenet@csusac.csus.edu (News account (alt))
Organization: California State University, Sacramento
Lines: 17

>> I have a slab running 2.0 with a terminal hanging off ttyb.  The getty
>> program is hogging alot of CPU time; notice the following samples:
>
>    Are you sure your serial line doesn't have the CD line asserted high all  
>the time?  This is one reason why your getty is getting all confused. Make sure  
>you only have CD high when you actually have something on the line.
>

One thing I've noticed with our terminals, is if I suddenly connect a
terminal to a port with a getty running on it, it redumps the getty
"login" message on the terminal. The ONLY lines connected are Send,
Receive, and Ground, and would thus indicate that the getty process
sits there looking for stop bits (Hi state). This might explain why
the getty hogs the cpu. I also noticed getty sucking the cpu at home
when my gs is off (However I did switch to ttydb, and it worked fine).

I also (just to try it) checked it under 2.1. Does the same thing.