Technical data

it allows users to submit print jobs using either the lpr or lpd client or
Advanced Printing CLI and GUI clients.
To direct incoming lpd print jobs to Advanced Printing printers, you must
create printcap entries on the print server host that associate LPD printers
(specified with the lpr requests) with Advanced Printing logical printers.
Such printcap entries declare the printer as a gateway printer. All jobs
submitted to a gateway printer are converted to Advanced Printing jobs and
are directed to the associated logical printer in an Advanced Printing spooler.
You identify an LPD printer as a gateway printer by including the
expressions rm=@dp and rp=<logical printer> in the print server
host’s printcap entry. You should also include the lp, sd, and mx options
to specify (1) the printer is not on a local port, (2) the spool directory, and
(3) the maximum job size, respectively. All other printcap flags in such
an entry are ignored.
The following example shows an /etc/printcap entry that specifies the
LPD printer bunker as a gateway printer associated with the Advanced
Printing logical printer named archie:
lp1|bunker|archie|Digital LN17ps:\
:lp=:\
:rm=@dpa:\
:rp=archie:\
:sd=/var/spool/printer/archie:\
:mx#0:
When an lpr client or a line printer daemon on another host passes a print
job to printer bunker, lpd passes the job through the Inbound Gateway to
the Advanced Printing logical printer archie.
The following example shows the corresponding printcap entry for the
client host:
lp1|bunker|Digital LN17ps:\
:lp=:\
:rm=<spooler hostname>:\
:rp=bunker:\
:mx#0:
You do not have to install Advanced Printing Software subsets on the client
hosts.
The Inbound Gateway daemon shares spool directories with the Advanced
Printing spooler or spoolers. When a job arrives at the Inbound Gateway,
and the gateway can directly access the spooler’s spool directory, the gateway
stores the document files in that directory for the spooler to access.
10–2 LPD Inbound Gateway Client Daemon