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
PRLCLEAN
INTERACT
$CMD_PR1$
$CMD_PR2$
$CMD_PR3$
$CMD_PR4$
$CMD_PR5$
$CMD_PR6$
$PROMPT$
That is correct!
You've got it on the 2nd try.
Good, you understand the concept.
$FIRST_F1$
$FIRST_F2$
$FIRST_F3$
$SECOND_F1$
$SECOND_F2$
$SECOND_F3$
I will help you this time.
$PROMPT$
FORGET1
$PROMPT$$ANSWER$
Observe the result on the terminal.
PAUSE
LNEXT
ENCORE2
$PROMPT$
DRAWTERM
TERMINAL
NEXT
$V1$
ENCORE1
BOTCLEAN
LINE
INTCMDS
Some of the interactive commands for the lpc program include:
? or help - prints description of commands.
abort - terminates specified spooling daemon or printer
clean - removes temporary files from specified printer queue
disable - turns the specified printer queue off
enable - enables spooling on specified queue
quit - exit from lpc
start - enable printing and start a spooling daemon for printer
status - display status of daemons and queues
AANVANG
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 the 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
there is the spooling scheduler is running.
To do this, you need to use the interactive /etc/lpc (line printer control)
command. This allows you to enable or disable a printer or its queue
and check the status of jobs. The interactive commands are listed
above.
$PROMPT$$ANSWER$
lpc>
Note the lpc prompt: lpc>
$PROMPT$$ANSWER$
laser1: queuing is enabled
printing is enabled
50 entries waiting
warning: no daemon present
$PROMPT$
Note that laser1 has a problem.
To fix it you need to abort the
printer.
$PROMPT$$ANSWER$
$PROMPT$
daemon (PID 5622) killed
$PROMPT$$ANSWER$
printing enabled
daemon started
$PROMPT$
Now the daemon should be running
again. You can check it as before
with the status command.
$PROMPT$$ANSWER$
$PROMPT$
Another problem that may occur is that the printer buffer
area becomes blocked for one reason or another. This may
block the print jobs or it may print the jobs when one
would not expect them, upon reboot, etc.
When there are no print requests on the system, and the
print area: /usr/spool/lgp has several files stacked
up you should remove them. This should occur only during
system crashes, or during some other unusual events.
Observe the result above.
total 656
-rw-rw---- 1 root 62 Apr 7 17:24 cfA158vaxA
-rw-rw---- 1 root 83 Apr 7 17:34 cfA159sunB
-rw-rw---- 1 root 641430 Apr 7 17:24 dfA158vaxA
-rw-rw---- 1 root 19818 Apr 7 17:34 dfA159sunB
-rw-r--r-- 1 root 17 Apr 7 17:24 lock
-rw-rw-r-- 1 root 26 Apr 7 17:24 status
Of course, as a last resort, you can recycle the power, but
this removes all of the jobs from the queue.
Before we leave this topic, remember that you can always use
the ps -ef command to determine the status of all processes
on your system.