Quick Start Guide
2
Change the option with lpadmin:
lpadmin -p
queue
-o Resolution=600dpi
3 Check the new setting:
lpoptions -p
queue
-l
Resolution/Output Resolution: 150dpi 300dpi *600dpi
When a normal user runs lpoptions, the settings are written to ~/.cups/lpoptions.
However, root settings are written to /etc/cups/lpoptions.
14.6 Printing from the Command Line
To print from the command line, enter lp -d
queuename filename
, substituting the
corresponding names for
queuename
and
filename
.
Some applications rely on the lp command for printing. In this case, enter the correct
command in the application's print dialog, usually without specifying
filename
. For
example: lp -d
queuename
.
14.7 Special Features in openSUSE
A number of CUPS features have been adapted for openSUSE. Some of the most
important changes are covered here.
14.7.1 CUPS and Firewall
After having performed a default installation of openSUSE, SuSEFirewall2 is active
and the network interfaces are congured to be in the External Zone which blocks
incoming trac. More information about the SuSEFirewall2 conguration is available
in Section “SuSErewall2” (Chapter 13, Masquerading and Firewalls, ↑Security Guide)
and at http://en.opensuse.org/SDB:CUPS_and_SANE_Firewall_settings.
14.7.1.1 CUPS Client
Normally, a CUPS client runs on a regular workstation located in a trusted network
environment behind a rewall. In this case it is recommended to congure the network
interface to be in the Internal Zone, so the workstation is reachable from within the
network.
14.7.1.2 CUPS Server
If the CUPS server is part of a trusted network environment protected by a rewall,
the network interface should be congured to be in the Internal Zone of the rewall.
It is not recommended to set up a CUPS server in an untrusted network environment
172 Start-Up










