sfrank@orion.oac.uci.edu (Steven Frank) (03/12/91)
A getty process that watches the serial port for login from a PC uses about 20% of my CPU time (68040, NS 2.0), even when competing with other processes for the CPU. The following shows my /etc/ttys file, and the output from ps before and after the getty process is killed. Note that a new getty comes up immediately after the kill, still using much CPU: fisher# cat /etc/ttys # # name getty type status comments # # If you do not want to start the window server by default, you can # uncomment the first entry and comment out the second. # # console "/usr/etc/getty std.9600" NeXT on secure . . ttya "/usr/etc/getty D9600" ansi off ttyb "/usr/etc/getty std.9600" vt100 on secure . . fisher# ps -aux | grep getty USER PID %CPU %MEM VSIZE RSIZE TT STAT TIME COMMAND root 3601 22.9 0.6 1.24M 256K b R 0:45 - std.9600 ttyb (getty) root 3620 0.0 0.5 1.31M 200K p3 S 0:00 grep getty fisher# who steve console Mar 5 12:41 steve ttyp1 Mar 5 12:41 steve ttyp2 Mar 8 16:41 steve ttyp3 Mar 11 21:09 fisher# kill -9 3601 fisher# !p ps -aux | grep getty USER PID %CPU %MEM VSIZE RSIZE TT STAT TIME COMMAND root 3622 19.7 0.6 1.24M 256K b S 0:02 - std.9600 ttyb (getty) I had used this configuration in 1.0 without any problems. Any suggestion would be appreciated. Steve Frank steve@fisher.bio.uci.edu