Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Planning a Workgroup
Planning your Printer Configuration
Chapter 2 113
Similarly, a priority fence value can be assigned to each printer to set the
minimum priority that a print request must have to print on that
printer. A printer’s fence priority is used to determine which print
requests get printed; only requests with priorities equal to or greater
than the printer’s fence priority get printed. See lpadmin (1M) and
lpfence (1M) for details.
Printer Logging
Every LP spooler system request is logged in a log file located in
/usr/spool/lp/log. The file contains a record of each LP spooler
system request, including request ID, user name, printer name, time,
error messages, and reprints due to failure.
Scalability and the LP Spooler
The LP spooler system serves routine print management quite
adequately. However, as technology needs have grown, the issue of
scalability has proven an obstacle for the LP spooler.
If you are administering a large-scale printing environment, the HP
Distributed Print Service (HPDPS) might be a preferable tool-set (see
“HP Distributed Print Service (HPDPS)” on page 113).
HPDPS (also referred to as DPS) allows users to use familiar LP spooler
commands, while giving you greater flexibility managing a complex print
environment. Conversely, HPDPS commands allow far greater specificity
in your print requests.
HP Distributed Print Service (HPDPS)
HP Distributed Print Service (HPDPS, also referred to as DPS) can be
used to great advantage in large, distributed environments that are
organized according to a client/server model and use DCE. HPDPS can
be configured in a Basic or Extended Environment.
IMPORTANT HPDPS is not supported on releases after HP-UX 11i Version 1
The following is a list of links in this module to print-management
concepts using HPDPS:
“What is HPDPS?” on page 114