Depends on what casued the port to lock up. Log in on another terminal and see what processes migh be still running on the port (ps -ef | grep tty1 | grep -v grep) and try to kill them. If it is a hung process killing said process should unlock the port.

After you killed the bash process on tty1 the system fired off a getty to look for a log in on that port. So as far as the system is concerned the port is ready for use. Since that tty is still hung there's something else locking it up. Other than some wierd video problem all that I can think of is that perhaps you hit Ctrl-S during the logout. That's an XOFF and would block further output to the port. Hitting CTRL-Q should clear that and release the port if that's the problem.

0

scronkeyAuthor Commented: 2004-09-22

Hi, thanks for your further investigation.

I have found the problem, similar to your suggestion here.
I would just like to confirm something for my own knowledge.

I tried hitting ctrl-q, to no avail. I tried ctrl-s & ctrl-q a few more times with no change.
Then I saw that scroll lock was on (d'uh) and this fixed it. (Thank you for helping out, even with such an embarrasing solution!)

What I would like to know is if scroll lock is simply toggling XON & XOFF?
I tested it on a functioning terminal (that had info scrolling in it) and ctrl-s AND scroll lock stop the scrolling. And ctrl-q started it again, as does scroll-lock.

So why, after hitting logout (then accidently hitting ctrl-s) does ctrl-q not work? Is it because the short-cut keys are no longer available?

I'm probably confusing myself more here, but this is the first time I've ever seen what scroll lock does/can do.