severyn@athena.ecs.csus.edu (Niles Severyn) (05/08/91)
Ok, I've been having problems with getty too. If someone logs in, and then runs a program and stops it with ^Z, and attempts to log out, the csh says "there are stopped jobs" and goes back to the prompt. If you attempt to log out again it does it, like it should, and kills off the process (I think). Now when the getty gets control, it dumps the "login" string, only it dumps it about 3 characters at a time, then pauses a couple seconds and sends the next 3 chars, etc. When you try to login, you get NO response from the getty AT ALL. If you edit the /etc/ttys file so that the getty is off, do a kill -HUP 1 and check the processes, the getty is still running. Even as root if you kill -9 on the process it WILL NOT DIE. The ONLY way I have to fix it is to reboot. I'm on a 68040 cube, with NS2.0, and the getty's are on ttya, ttyb and ttydb. It doesn't matter which tty it is, they all lock up. Also, the terminals only have 3 lines connected, Send, Receive, and ground, however the modem (ttydb) has the DTR and CD lines connected as well, so that I can dial out with cub, and it will hang up the line on log out.