Shared printers can be difficult to maintain because of the multiple processes that interact before the job is output. For this section, a shared printer had been previously started with the command startshp 3,1,0,s17,lp.unix.
When a problem occurs, follow this troubleshooting list:
Verify that the UNIX queue is started by typing:
|
lpstat |
The designated queue should display as Ready.
Verify the D3 printer status at TCL by typing:
|
shp-status |
This command displays some information on the status of the D3 printer process and its associated filter.
Verify if there is a UNIX process started on the D3 line number at TCL by typing:
|
pid line.number |
The result should display a nonzero PID.
Verify that the filter process is running by typing:
|
ps aux | grep lppick |
The filter program and some of its options should display.
(Optional) Kill the shared printer by executing the steps below if the shared printer cannot be restarted after using shp-kill.
|
startshp 3,1,0,s17,lp.unix |
Use the sp-kill command to kill the printer.
|
sp-kill d3 |
Manually kill the UNIX printer process.
|
kill p17 |
Remove the file /tmp/lppick.
|
!rm /tmp/lppick/pick0_3_17 |
Restart the printer.
If any of these steps do not provide the expected result, try to restart the shared printer with the startshp command.
|
NOTE |
The startshp command has some tracing facility. See the D3 Reference Manual for more details. |
See Also