pyrros@cis.udel.edu (Christos Pyrros) (05/06/91)
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: USER PID %CPU %MEM VSIZE RSIZE TT STAT TIME COMMAND root 683 23.5 2.1 1.24M 168K b S 22:06 - std.9600 ttyb (getty) root 683 20.6 2.1 1.24M 168K b R 22:07 - std.9600 ttyb (getty) root 683 16.5 2.1 1.24M 168K b R 22:18 - std.9600 ttyb (getty) root 683 30.1 2.1 1.24M 168K b R 22:20 - std.9600 ttyb (getty) root 683 26.6 2.1 1.24M 168K b R 22:23 - std.9600 ttyb (getty) root 683 25.9 2.1 1.24M 168K b R 22:25 - std.9600 ttyb (getty) You get the idea! Someone told me this might be a bug with the serial drivers in 2.0. Is that accurate? I have a 105 Meg HD, and I don't think it would be worth upgrading to 2.1 before I get an nice, fat, juicy external HD. Any ideas for quick fixes besides staying logged in all the time? Thanks, Chris
jiro@shaman.com (Jiro Nakamura) (05/07/91)
In article <52694@nigel.ee.udel.edu> pyrros@cis.udel.edu (Christos Pyrros) writes: > 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. - jiro -- Jiro Nakamura jiro@shaman.com Shaman Consulting (607) 253-0687 VOICE "Bring your dead, dying shamans here!" (607) 253-7809 FAX/Modem
severyn@athena.ecs.csus.edu (Niles Severyn) (05/16/91)
>> 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.