Fixing hung terminals
A terminal is considered ``hung'' if the previous work
session is still visible on the display, but it does not
respond to keyboard input. To fix a hung terminal:
If the ps -t command shows only a getty
program, the terminal should display a login prompt.
If it does not, check the terminal hardware again.
Wait a minimum of 60 seconds before trying to resurrect the
terminal. (If the system is busy, the terminal may not
respond immediately to keystrokes because the system
response time has increased.)
Press <Ctrl>q to re-enable transmission in case
the <Ctrl>s (transmit off) signal was
Check to see that all power cords, keyboard cords, and
communications cables are connected.
Reset the terminal hardware by recycling power to the
terminal and then reinitialize it by running
with no arguments.
Verify the terminal set-up mode configuration settings
(if available) as described in step 3 of the previous section.
Test the hardware communications by redirecting output from
an operating terminal to the locked one as described
in the step 6 of previous section.
Check the processes that are running on the locked
terminal port with the following command:
ps -t ttyline
Stop the process that the user was running when
the terminal hung using
``Killing a process''.)
If the program does not die, you must reboot
the system to stop the process.
Determine whether the current line characteristic
parameters are correct.
For example, use the following command to display
these values for tty2a:
stty -a < /dev/tty2a
You can also compare the stty settings with those of
a working terminal.
Reset the serial line characteristics with the following command:
<Ctrl>j stty sane <Ctrl>j
If you cannot enter the command on the terminal, you can redirect
the stty command from another terminal as follows:
stty sane < /dev/tty2a
Fixing scrambled terminal display
Restoring non-functional terminals
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 03 June 2005