90
Print Queues
Berkeley Software Distribution
Berkeley Software Distribution (BSD)-Style Print Queue
BSD is a version of the UNIX OS that includes TCP/IP.
Configuring the Print Queue
For remote
Important • You must be logged in as root.
The entry looks similar to this:
local_print_queue_name[printer_model_and_manufacturer]:\ :lp=:mx#0:rm=BradyConnect_name:\ :rp=remote_print_queue_name:\ :sd=path_to_spool_directory:lf=just log_file_name
local_print_queue_name — This defines the name of the printcap entry. It is used by the LPR/LPD utilities to specify which printcap entry is being referenced. Additional printcap entries can be added as needed for different queue types. Each entry must have a unique local_print_queue_name and a different spool directory to work properly. When you are ready to print, use the local_print_queue_name that matches the data type of the file to be printed.
BradyConnect_name — This is the name (alias) of the BradyConnect 10/100 Internal PS. This must be the same name as entered in the /etc/ hosts file or your NIS or DNS system. An IP address may also be used here.
remote_print_queue_name — This entry determines the BradyConnect port where the print job will be printed and optionally specifies ASCII printing that must end for LF1.
path_to_spool_directory — This is the path to a directory where the print jobs will be spooled for this queue. You must create a unique spool directory for each printcap entry.
log_file_name — This is the path to a file where error information from the LPD will be logged.
Example • Your printcap entries might look similar to this:
Ascii_filesform.feed.Queue_on_Port_1:\ :lp=:mx#0:rm=pserver1:rp=MYQUEUELF1:\ :sd=/usr/spool/myqueuelf1:\
:lf=/usr/spool/myqueuelf1/queue.log
Important • Each printcap entry must have a different spool directory to work properly.
Y885775 | BradyConnect 10/100 Internal Print Server User Guide | 07/18/2008 |
