Configuring HP-UX For Peripherals

Chapter 4 129
Configuring Terminals and Modems
Troubleshooting Terminal Problems
Troubleshooting Terminal Problems
This section addresses problems with alphanumeric display terminals;
however, the techniques can be applied to problems with terminal
emulators such as AdvanceLink or X-Windows terminal processes (such
as hpterm and xterm).
Unresponsive Terminals
Several conditions can cause a terminal not to display any characters
except for those it echoes when you type. Proceed through these steps
(working from an active terminal) to solve many of them.
Step 1. Check the status of the system. If the system is still running, try
resetting the terminal.
If the system is in single-user mode, the only active terminal will be the
system console; other terminals will not respond. Switch to a multi-user
state. Consult the init (1m) manpage in the HP-UX Reference for
information on changing run levels.
Check your system run-level as follows:
who -r
. run-level 2 Sep 28 10 07:10 2 0 S
The current state of the machine (run-level 2 in this example) is shown
in the highlighted field. For complete information on each of the fields,
consult the who (1) manpage.
Step 2. Look for an editor running on the terminal. Examine the active
processes associated with the unresponsive terminal and look for an
editor (such as an active vi process). For example, for terminal tty0p1,
/etc/fuser /dev/tty0p1
or
ps -t tty0p1 -f
If you find an active editor process running at the terminal, it is probably
in a text-entry mode. You will need to save the work to a temporary file
and exit the editor. If you are not sure of the status of the work being
edited, do not simply save the file and exit. You will overwrite the
previous contents of the file with unknown text. Save the