Setting up workstations

The following example shows printcap entries for a printer named “Perfector.” The printer controller is registered as “perfector.” An additional virtual printer, “Perfector-duplex,” is defined for duplex printing.

Perfectordocuprint in 2301:\ :rp=perfector:rm=perfector:\

:sd=/var/spool/perfector:mx#0:lp=:

Perfector-duplexdocuprint in 2301duplex:\

:rp=perfector-duplex:rm=perfector:\ :sd=/var/spool/perfector:mx#0:lp=

Solaris

The following instructions are specific to the operation of Solaris lp for submission to the printer. Submission using lp on the DocuPrint controller is NOT supported.

NOTE: The printer controller Sun operating system is based on the standard Sun operating system; however, it has been customized for use with the Xerox printer controller. Therefore, not all standard Sun operating system features are available.

While the instructions for editing the /etc/printcap file are generic for SunOS 4.x UNIX systems using lpr, the systems that use lp operate differently on each UNIX platform. Solaris administrators should consult their man pages or the Solaris Answerbook for more information on the commands used below. Solaris Admintool is NOT recommended, because the “remote system type” option is not supported.

At the client, login as root (except lpstat).

To start the print service: /etc/init.d/lp start

To stop the print service: /etc/init.d/lp stop

To identify the DocuPrint and its type:

lpsystem -t bsd -T 1 -R 1 -y“description of printer” NPS/ IPS_hostname

where:

-t bsd defines the DocuPrint system as a berkeley spooler

-T 1 defines the timeout parameter

-R 1 defines the retry parameter

-y ascii field for “description of printer” must be in quotes

2-18

Guide to Submitting Jobs from the Client

Page 46
Image 46
Xerox 721P90350 manual Solaris