[comp.sys.next] Getty hogging CPU, again!

pyrros@cis.udel.edu (Christos Pyrros) (05/17/91)

Well, you all remember how my get-hogging-cpu problem was solved by using
ttydb instead of ttyb.

THAT was on 2.0.  I just got 2.1.

Surprise, surprise, it's screwed up again.  Notice these samples:

USER       PID  %CPU %MEM VSIZE RSIZE TT STAT  TIME COMMAND
root       153  15.4  2.3 1.24M  192K db R    50:04 - std.9600 ttydb (getty)

root       153  21.7  2.3 1.24M  192K db R    50:06 - std.9600 ttydb (getty)

Although the terminal works fine, this cpu-hogging really slows things down.
So why does this happen?  What did 2.1 do to make this problem reappear?

I'll eventually dropping an Ethernet card (~$180) into my 8088 doorstop
so I can free up a serial port, but until then I would like to get this 
solved. 

Oh, also, this is a slab, 8/105, 2.1.  I only have RxD and TxD hooked up.
Some people suggested I need to hook up DTR and DSR?

Thanks,

Chris