HP-UX System Administrator's Guide: Routine Management Tasks

from the terminal to the computer, it can be restarted by sending the computer an
XON signal (type ctrl-q from the problem terminal’s keyboard). Sending the XON
signal does not harm anything even if no XOFF signal was previously sent.
If the problem is an application program that’s looping or not functioning properly,
try pressing the break key and then try ctrl-C to see if you can get a shell prompt
back (ctrl-C is the default interrupt character; you might use a different one). If
you need to find out what the interrupt character for the affected terminal is, go
to a working terminal and enter the command:
stty < /dev/device_filename_for_the_problem_terminal
CAUTION: The stty command, above, should only be used with device file
names for currently active terminal device files (use the who command to see
which device files are active). If you attempt to execute stty with a non-active
device file, you will hang the terminal where you entered the commands.
4. Reset the terminal.
The terminal itself may be stuck in an unusable state. Try resetting it. Consult your
terminal owner’s manual for information on how to do this. Powering the terminal
off, waiting for a few seconds and powering it back on will also reset the terminal.
5. Check the terminal configuration.
The terminal might not be configured correctly. You should check the following:
• Is the terminal in Remote * mode? It should be.
• Is Block * mode turned ON? It shouldn’t be.
• Is Line * mode turned ON? It shouldn’t be.
• Is Modify * mode turned ON? It shouldn’t be.
6. Check the physical connection.
Check to make sure that:
• All cables are firmly attached and in their proper locations.
• All interface cards are firmly seated in their slots.
• The power cord to the terminal is firmly connected.
• The power switch is turned on.
7. Kill processes associated with the problem terminal.
CAUTION: Use extreme caution when killing processes. The processes will be
immediately and unconditionally terminated. Some valid processes might take a
long time to complete. Be sure to type carefully when entering the PID numbers
for the killcommand to avoid killing the wrong process.
If you have another terminal that is still working, go to that terminal and log in
(you will need to be superuser). Execute the command:
158 Managing Systems