LNEXT
ONELCLEAN
BOTCLEAN
UTERMINAL
TERMINAL
NEXT
$V1$
HILINE
PAUSE
q to quit, <CR> to continue
PRSICK
|~~~~~~~~~~~~~|
PRINTER
|
-
|
UNIX
COMPUTER
SICK2PR
|/^v///^^^^\\\| <--- Jammed ?
*** On-line ?
PRINTER --------------\ |
\-------<|
| Connected ? |
SICK3PR
|~~~~~~~~~~~~~|
1. Serial vs. parallel mode?
2. Proper character set?
PRINTER 3. Proper parity for serial printer?
4. Correct number of data and stop
| bits for serial printer, etc.?
STUCKPR
d0-2553
d0-2554
r-2553
r-2554
GO
If your printer was working fine, but suddenly does not produce
the output you expect or produces printouts you did not expect,
then before taking it in for service, please do some checking on
your own.
First of all, check the hardware setup:
1. Is the printer on-line?
2. Is the paper jammed in the printer?
3. Is the printer cable properly connected to your system?
If the printer hardware is properly connected,
the next thing you should check is the printer setup.
You may need to refer to your owner's manual
to check the printer's parameters.
Some parameters to check include:
1. Is the printer set to serial instead of parallel mode, or vice-versa?
2. Is the XON/XOFF properly set?
3. Is the proper character set selected?
4. Is the buffer size properly selected?
Normally the printer problem is the spooling system software
on your UNIX system.
In this case, the first thing you need to check is whether
the spooling scheduler is running.
The command to do this is:
lpstat -r
Please practice this command now.
$PROMPT$
That is correct!
You've got it on the 2nd try.
Good, you understand the concept.
Please type lpstat -r
Please type lpstat -r
You will be helped this time!
FORGET2
lpstat -r
scheduler is not running
$PROMPT$
If you have a problem with the
printer scheduler, you need to enter
rm -f /usr/spool/lp/SCHEDLOCK to
prevent more than one version of
the line printer scheduler to
run at any one time. Practice
this command at the prompt.
$PROMPT$
That is correct!
You've got it on the 2nd try.
Good, you understand the concept.
Please type
rm -f /usr/spool/lp/SCHEDLOCK
Please type
rm -f /usr/spool/lp/SCHEDLOCK
You will be helped this time!
FORGET4
rm -f /usr/spool/lp/SCHEDLOCK
Please observe the result.
$PROMPT$
Now restart the spooling scheduler
again by typing:
/usr/lib/lpsched
$PROMPT$
That is correct!
You've got it on the 2nd try.
Good, you understand the concept.
Please type /usr/lib/lpsched
Please type /usr/lib/lpsched
You will be helped this time!
FORGET3
/usr/lib/lpsched
Now lpsched should be running
again. You can check it as before
with the lpstat -r command.
Another problem that may occur from time to time is
that the printer buffer area becomes blocked for one reason
or another. This may either stop the print jobs or it may print
the jobs when one would not expect them, i.e., upon reboot, etc.
When there are no print requests on the system, and the print area
/usr/spool/lp/request/printer-name has several files
stacked up you should remove them. This should occur only during
system crashes, or during some other unusual events.
Assuming that the default printer
name on your system is printer,
determine if there are any files
still left over in the printer
default buffer directory by typing:
ls /usr/spool/lp/request/printer
$PROMPT$
That is correct!
You've got it on the 2nd try.
Good, you understand the concept.
Please type
ls /usr/spool/lp/request/printer
Please type
ls /usr/spool/lp/request/printer
You will be helped this time!
FORGET5
ls /usr/spool/lp/request/printer
$PROMPT$
One more reminder: you can always use
the ps -ef command to determine
the status of all processes on your
system.