Xerox DocuColor 240-250 con Xerox FreeFlow DXP250-14674 - Manual (Page 12)

Installation Using the lp Utilities for Solaris
On a Solaris 2.5.1 or earlier client
The –o options are ignored when using lp on a Solaris 2.5.1 or
earlier client and submitting jobs to the controller. To correct this,
perform the following on the client workstation:
1. Open a command tool and enter the following:
lpsystem -l
This will list all the remote printers and the associated lp
properties that have been created on the Solaris 2.5.1 client
workstation. The following is an example:
System: polaris
Type: bsd
Connection timeout: never
Retry failed connections: after 10 minutes
Comment: allow all connections
The entry after System denotes the name of the remote printer,
which should represent the controller name. If the Type identified
for the remote printer is set to bsd, then the remote printer is
configured correctly and will print successfully to the printer
controller once the svr4–extensions entry has been added to
the /etc/lp/Systems file (detailed below).
NOTE: When creating a remote printer using the Solaris
Admintool Utility on a Solaris 2.5.1 client, all printers by default
are bsd.
If the type is set to s5, you will not be able to print from your
Solaris 2.5.1 client to the controller since Solaris 2.6 no longer
supports the System V print protocol. The Type will need to be
changed to bsd. To make this change, do the following:
1. In a command tool window, enter the following:
lpsystem -t bsd
2. Locate the /etc/lp/Systems file.
3. Edit the remote printer entry for the controller in the Systems
file. The following is an example of an old entry in the
Systems file:
:x:-:bsd:-:n:10:-:-:
Using a text editor, change the entry to the following:
:x:-:bsd:-:n:10:svr4­
extensions:-:
4. Enter the following in the Command Tool:
1-4