Technical data

2. Make sure the server is not actively printing jobs to printers by verifying
that the physical printers are not in the printing state.
3. Check for any paused jobs on printers. The supervisor will not shut down
when jobs are paused unless you specify -w now with the pdshutdown
command.
4. If you still cannot stop the supervisor process, determine the supervisor’s
PID and use kill -9 to terminate it.
# pdls -c printer servername:
printer-name printer-realization printer-state enabled
------------ ------------------- ------------- -------
LN17ps_PP physical idle yes
LGP physical idle no
Richs_PP physical idle no
Sharie_PP physical idle no
LN03R physical idle no
ln17bert physical idle no
lps17_sue physical idle no
Null_PP physical idle no
# ps ax | grep pds
29874 ?? I 0:00.64 /usr/pd/lib/pdsplr merle_spl
30481 ?? S 0:34.69 /usr/pd/lib/pdspvr merle_sup
5008 ttyp7 S + 0:00.02 grep pds
# kill -9 30481
12.1.4 Spooler Will Not Shut Down
Use the same procedure as described in Section 12.1.3, to stop a spooler
process.
12.2 Solving Job and Print Problems
This section contains descriptions of job and print errors that can occur
during normal print system operation. Note that while these errors are
characterized as job and print errors, this does not necessarily mean that
the errors are caused only by print and job objects, they might be caused
by other objects in the print system.
12.2.1 PostScript Documents Print PostScript Program Code
Some applications that produce PostScript code incorrectly omit the
PostScript lead-in sequence %!. If your document does not begin with those
characters, the print system supervisor incorrectly determines that the file
is a text file and translates it to a text listing rather than letting the printer
interpret it.
Troubleshooting 12–3