User Guide

1-3
3.
✒ Note
This step applies to the majority of UNIX systems, including Sun OS (but not Solaris 2.xx),
Silicon Graphics (lpr/lpd option required), DEC ULTRIX, DEC OSF/1, and Digital UNIX.
SCO UNIX users should follow these steps, but should also refer to the SCO UNIX
Configuration section. Users of RS/6000 AIX, HP/UX, Sun Solaris 2.xx, and other systems
that do not use the printcap file.
Configure the
/etc/printcap
file on each host computer to specify the local print
queue, the print server name (also called remote machine or rm), and the print server
service name (also called remote printer, remote queue, or rp), and the spool directory.
An example of a typical
printcap
file:
laser1|Printer on Floor 1:\
:lp=:\
:rm=BRN_310107:\
:rp=TEXT_P1_TX:\
:sd=/usr/spool/lpd/laser1:
✒ Note
Make sure this information is added to the end of the
printcap
file. Also make sure that the
last character in the printcap file is a colon ":"
This will create a queue named
laser1
on the host computer that communicates to a
Brother print server with a node name
(rm)
of BRN_
310107
and a service name
(rp)
of
TEXT_P1_ TX printing text files to a Brother printer through spool directory
/usr/spool/lpd/laser1
. If you are printing binary graphics files, you would use
the service BINARY_P1 instead of TEXT_P1_ TX.
✒ Note
The
rm
and
rp
options are not available on some UNIX systems, so if necessary check your
documentation (or man pages) to determine the equivalent options.
Users of Berkeley-compatible UNIX systems can use the lpc command to obtain the
printer status:
%lpc status
laser1:
queuing is enabled
printing is enabled
no entries
no daemon present
Users of AT&T-compatible UNIX systems can generally use the
lpstat
or
rlpstat
commands to obtain similar status information. Because this procedure varies from system
to system, refer to your system documentation for the exact usage.