+ +
CUPS Software Administrators Manual
-CUPS-SAM-1.1.8
+CUPS-SAM-1.1.23
Easy Software Products
-Copyright 1997-2001, All Rights Reserved
+Copyright 1997-2005, All Rights Reserved
+
Table of Contents
Preface @@ -50,36 +50,42 @@ Copyright 1997-2001, All Rights Reserved
2 - Building and Installing CUPS
-
-
- Installing a Source Distribution +
- Installing a Source Distribution -
- Installing a Binary Distribution + +
- Installing a Binary Distribution +
- The Basics -
- Adding Your First Printer +
- Adding Your First Printer -
- Managing Printers from the Command-Line + +
- Managing Printers from the Command-Line +
- Managing Printers from the Web
5 - Client Setup 6 - Printing System Management
- The Basics
- Restarting the CUPS Server
- Changing the Server Configuration -
- Server Directives +
- Server Directives
- AccessLog
- Allow @@ -115,15 +124,18 @@ Copyright 1997-2001, All Rights Reserved
- BrowseAddress
- BrowseAllow
- BrowseDeny -
- BrowseOrder
- BrowseInterval +
- BrowseOrder
- BrowsePoll
- BrowsePort +
- BrowseProtocols
- BrowseRelay
- BrowseShortNames
- BrowseTimeout
- Browsing
- Classification +
- ClassifyOverride +
- ConfigFilePerm
- DataDir
- DefaultCharset
- DefaultLanguage @@ -131,11 +143,18 @@ Copyright 1997-2001, All Rights Reserved
- DocumentRoot
- Encryption
- ErrorLog +
- FaxRetryInterval +
- FaxRetryLimit +
- FileDevice
- FilterLimit +
- FilterNice
- FontPath
- Group +
- HideImplicitMembers
- HostNameLookups +
- ImplicitAnyClasses
- ImplicitClasses +
- Include
- KeepAlive
- KeepAliveTimeout
- Limit @@ -143,8 +162,11 @@ Copyright 1997-2001, All Rights Reserved
- LimitRequestBody
- Listen
- Location +
- LogFilePerm
- LogLevel
- MaxClients +
- MaxClientsPerHost +
- MaxCopies
- MaxJobs
- MaxJobsPerPrinter
- MaxJobsPerUser @@ -153,20 +175,26 @@ Copyright 1997-2001, All Rights Reserved
- Order
- PageLog
- Port -
- PreserveJobHistory
- PreserveJobFiles +
- PreserveJobHistory
- Printcap -
- PrintcapFormat +
- PrintcapFormat +
- PrintcapGUI +
- ReloadTimeout
- RemoteRoot
- RequestRoot +
- Require
- RIPCache +
- RootCertDuration
- RunAsUser +
- Satisfy
- ServerAdmin
- ServerBin
- ServerCertificate
- ServerKey
- ServerName
- ServerRoot +
- ServerTokens
- SSLListen
- SSLPort
- SystemGroup @@ -174,71 +202,140 @@ Copyright 1997-2001, All Rights Reserved
- Timeout
- User
- Printing System Security + +
- Changing the Client Configuration +
- Client Directives
+
-
+
- Encryption +
- ServerName +
+ - Changing the Printer Configuration +
- Printer Directives + + +
- Changing the Classes Configuration +
- Classes Directives
+
-
+
- Accepting +
- AllowUser +
- Class +
- DefaultClass +
- DenyUser +
- Info +
- JobSheets +
- KLimit +
- Location +
- PageLimit +
- Printer +
- QuotaPeriod +
- State +
- StateMessage +
+ - Printing System Security -
- Printer Accounting + +
- Printer Accounting -
- File Typing and Filtering + +
- File Typing and Filtering +
- The Basics
- Printing from LPD Clients -
- Printing to LPD Servers -
- Printing from Mac OS Clients +
- Printing to LPD Servers +
- Printing from Mac OS 10.2 and Later Clients +
- Printing from Mac OS 10.1 and Earlier Clients + + +
- Printing to Mac OS 10.2 and Later Servers +
- Printing to Mac OS 10.1 and Earlier Servers +
- Printing from Windows Clients -
- Printing to Mac OS Servers -
- Printing from Windows Clients -
- Printing to Windows Servers + +
- Printing to Windows Servers
-
-
- Common UNIX Printing System License Agreement +
- Common UNIX Printing System License Agreement + +
- GNU GENERAL PUBLIC LICENSE
+
-
+
- Preamble +
+ - GNU LIBRARY GENERAL PUBLIC LICENSE + -
- GNU GENERAL PUBLIC LICENSE -
- GNU LIBRARY GENERAL PUBLIC LICENSE +
-
-
- Configuring a Network Interface +
- Configuring a Network Interface +
- Verifying the Printer Connection
- Common Network Interface Settings
- Configuring Axis Print Servers
- Configuring Linksys Print Servers +
- Configuring LPD Printing Options
- Printer Drivers +
- DYMO Label Printer
- EPSON 9-pin Dot Matrix
- EPSON 24-pin Dot Matrix
- EPSON Stylus Color @@ -252,39 +349,49 @@ Copyright 1997-2001, All Rights Reserved
- My Applications Don't See the Available Printers
- CUPS Doesn't Recognize My Username or Password! -
- I Can't Do Administration Tasks from Another -Machine! +
- I Can't Do Administration Tasks from Another + Machine!
- I Can't Do Administration Tasks from My Web Browser!
- Connection Refused Messages
- Write Error Messages
+
Preface
-This software administrators manual provides printer administration -information for the Common UNIX Printing SystemTM ("CUPS -TM"), version 1.1.8.
+This software administrators manual provides printer administration + information for the Common UNIX Printing SystemTM ("CUPS +TM"), version 1.1.23.
System Overview
-CUPS provides a portable printing layer for UNIX®-based operating -systems. It has been developed by Easy -Software Products to promote a standard printing solution for all -UNIX vendors and users. CUPS provides the System V and Berkeley -command-line interfaces.
-CUPS uses the Internet Printing Protocol ("IPP") as the basis for -managing print jobs and queues. The Line Printer Daemon ("LPD") Server -Message Block ("SMB"), and AppSocket (a.k.a. JetDirect) protocols are -also supported with reduced functionality. CUPS adds network printer -browsing and PostScript Printer Description ("PPD") based printing -options to support real-world printing under UNIX.
-CUPS also includes a customized version of GNU Ghostscript -(currently based off GNU Ghostscript 5.50) and an image file RIP that -are used to support non-PostScript printers. Sample drivers for HP and -EPSON printers are included that use these filters.
+CUPS provides a portable printing layer for UNIX®-based operating + systems. It has been developed by Easy + Software Products to promote a standard printing solution for all + UNIX vendors and users. CUPS provides the System V and Berkeley + command-line interfaces.
+CUPS uses the Internet Printing Protocol ("IPP") as the basis for + managing print jobs and queues. The Line Printer Daemon ("LPD") Server + Message Block ("SMB"), and AppSocket (a.k.a. JetDirect) protocols are + also supported with reduced functionality. CUPS adds network printer + browsing and PostScript Printer Description ("PPD") based printing + options to support real-world printing under UNIX.
+CUPS includes an image file RIP that supports printing of image files + to non-PostScript printers. A customized version of GNU Ghostscript + 7.05 for CUPS called ESP Ghostscript is available separately to support + printing of PostScript files within the CUPS driver framework. Sample + drivers for Dymo, EPSON, HP, and OKIDATA printers are included that use + these filters.
+Drivers for thousands of printers are provided with our ESP Print Pro + software, available at:
++ http://www.easysw.com/printpro/ ++
CUPS is licensed under the GNU General Public License and GNU Library + General Public License. Please contact Easy Software Products for + commercial support and "binary distribution" rights.
Document Overview
-This software administrators manual is organized into the following -sections:
+This software administrators manual is organized into the following + sections:
- 1 - Printing System Overview
- 2 - Building and Installing CUPS @@ -300,16 +407,16 @@ sections:
- E - Troubleshooting Common Problems
Notation Conventions
-Various font and syntax conventions are used in this guide. Examples -and their meanings and uses are explained below: +
Various font and syntax conventions are used in this guide. Examples + and their meanings and uses are explained below:
| Example | Description | ||
|---|---|---|---|
lpstat
- lpstat(1) | The names of commands; -the first mention of a command or function in a chapter is followed by -a manual page section number. | The names of commands; + the first mention of a command or function in a chapter is followed by + a manual page section number. | |
| /var
/usr/share/cups/data/testprint.ps | @@ -319,204 +426,206 @@ File and directory names. | Screen output. | |
| lp -d printer filename ENTER | - | Literal user input; special keys like ENTER are + | Literal user input; special keys like ENTER are in ALL CAPS. |
| 12.3 | Numbers in the text are -written using the period (.) to indicate the decimal point. | ||
| 12.3 | Numbers in the text are + written using the period (.) to indicate the decimal point. |
Abbreviations
- The following abbreviations are used throughout this manual: + The following abbreviations are used throughout this manual:- kb +
- kb
- Kilobytes, or 1024 bytes
-
- - Mb +
- Mb
- Megabytes, or 1048576 bytes
-
- - Gb +
- Gb
- Gigabytes, or 1073741824 bytes
-
+
-
-
+
+
Other References
- CUPS Software Programmers Manual -
- A programmer guide for interfacing with and/or extending the CUPS +
- CUPS Software Programmers Manual +
- A programmer guide for interfacing with and/or extending the CUPS
software.
-
- - CUPS Software Users Manual +
- CUPS Software Users Manual
- An end-user guide for using the CUPS software.
-
+
-
-
+
1 - Printing System Overview
-This chapter provides an overview of how the Common UNIX Printing -System works.
+This chapter provides an overview of how the Common UNIX Printing + System works.
The Printing Problem
-For years the printing problem has plagued UNIX. Unlike -Microsoft® Windows® or Mac OS, UNIX has no standard interface or system -in place for supporting printers. Among the solutions currently -available, the Berkeley and System V printing systems are the most -prevalent.
-These printing systems support line printers (text only) or -PostScript printers (text and graphics), and with some coaxing they can -be made to support a full range of printers and file formats. However, -because each varient of the UNIX operating system uses a different -printing system than the next developing printer drivers for a wide -range of printers and operating systems is extremely difficult. That -combined with the limited volume of customers for each UNIX varient has -forced most printer vendors to give up supporting UNIX entirely.
-CUPS is designed to eliminate the printing problem. One -common printing system can be used by all UNIX varients to support the -printing needs of users. Printer vendors can use its modular filter -interface to develop a single driver program that supports a wide range -of file formats with little or no effort. Since CUPS provides both the -System V and Berkeley printing commands, users (and applications) can -reap the benefits of this new technology with no changes.
+For years the printing problem has plagued UNIX. Unlike + Microsoft® Windows® or Mac OS, UNIX has no standard interface or system + in place for supporting printers. Among the solutions currently + available, the Berkeley and System V printing systems are the most + prevalent.
+These printing systems support line printers (text only) or + PostScript printers (text and graphics), and with some coaxing they can + be made to support a full range of printers and file formats. However, + because each varient of the UNIX operating system uses a different + printing system than the next developing printer drivers for a wide + range of printers and operating systems is extremely difficult. That + combined with the limited volume of customers for each UNIX varient has + forced most printer vendors to give up supporting UNIX entirely.
+CUPS is designed to eliminate the printing problem. One common + printing system can be used by all UNIX varients to support the + printing needs of users. Printer vendors can use its modular filter + interface to develop a single driver program that supports a wide range + of file formats with little or no effort. Since CUPS provides both the + System V and Berkeley printing commands, users (and applications) can + reap the benefits of this new technology with no changes.
The Technology
-CUPS is based upon an emerging Internet standard called the Internet -Printing Protocol. IPP has been embraced by dozens of printer and -printer server manufacturers and is supported by Microsoft Windows -2000.
-IPP defines a standard protocol for printing as well as managing -print jobs and printer options like media size, resolution, and so -forth. Like all IP-based protocols, IPP can be used locally or over the -Internet to printers hundreds or thousands of miles away. Unlike other -protocols, however, IPP also supports access control, authentication, -and encryption, making it a much more capable and secure printing -solution than older ones.
-IPP is layered on top of the Hyper-Text Transport Protocol ("HTTP") -which is the basis of web servers on the Internet. This allows users to -view documentation, check status information on a printer or server, -and manage their printers, classes, and jobs using their web browser.
-CUPS provides a complete IPP/1.1 based printing system that provides -Basic, Digest, and local certificate authentication and user, domain, -or IP-based access control. TLS encryption will be available in future -versions of CUPS.
+CUPS is based upon an emerging Internet standard called the Internet + Printing Protocol. IPP has been embraced by dozens of printer and + printer server manufacturers and is supported by Microsoft Windows + 2000.
+IPP defines a standard protocol for printing as well as managing + print jobs and printer options like media size, resolution, and so + forth. Like all IP-based protocols, IPP can be used locally or over the + Internet to printers hundreds or thousands of miles away. Unlike other + protocols, however, IPP also supports access control, authentication, + and encryption, making it a much more capable and secure printing + solution than older ones.
+IPP is layered on top of the Hyper-Text Transport Protocol ("HTTP") + which is the basis of web servers on the Internet. This allows users to + view documentation, check status information on a printer or server, + and manage their printers, classes, and jobs using their web browser.
+CUPS provides a complete IPP/1.1 based printing system that provides + Basic, Digest, and local certificate authentication and user, domain, + or IP-based access control. TLS encryption will be available in future + versions of CUPS.
Jobs
-Each file or set of files that is submitted for printing is called a -job. Jobs are identified by a unique number starting at 1 and are -assigned to a particular destination, usually a printer. Jobs can also -have options associated with them such as media size, number of copies, -and priority.
+Each file or set of files that is submitted for printing is called a + job. Jobs are identified by a unique number starting at 1 and are + assigned to a particular destination, usually a printer. Jobs can also + have options associated with them such as media size, number of copies, + and priority.
Classes
-CUPS supports collections of printers known as classes. Jobs -sent to a class are forwarded to the first available printer in the -class.
+CUPS supports collections of printers known as classes. Jobs + sent to a class are forwarded to the first available printer in the + class.
Filters
-Filters allow a user or application to print many types of files -without extra effort. Print jobs sent to a CUPS server are filtered -before sending them to a printer. Some filters convert job files to -different formats that the printer can understand. Others perform page -selection and ordering tasks.
-CUPS provides filters for printing many types of image files, -HP-GL/2 files, PDF files, and text files. CUPS also supplies PostScript -and image file Raster Image Processor ("RIP") filters that convert -PostScript or image files into bitmaps that can be sent to a raster -printer.
+Filters allow a user or application to print many types of files + without extra effort. Print jobs sent to a CUPS server are filtered + before sending them to a printer. Some filters convert job files to + different formats that the printer can understand. Others perform page + selection and ordering tasks.
+CUPS provides filters for printing many types of image files, HP-GL/2 + files, PDF files, and text files. CUPS also supplies PostScript and + image file Raster Image Processor ("RIP") filters that convert + PostScript or image files into bitmaps that can be sent to a raster + printer.
Backends
-Backends perform the most important task of all - they send the -filtered print data to the printer.
-CUPS provides backends for printing over parallel, serial, and USB -ports, and over the network via the IPP, JetDirect (AppSocket), and -Line Printer Daemon ("LPD") protocols. Additional backends are -available in network service packages such as the SMB backend included -with the popular SAMBA software.
-Backends are also used to determine the available devices. On -startup each backend is asked for a list of devices it supports, and -any information that is available. This allows the parallel backend to -tell CUPS that an EPSON Stylus Color 600 printer is attached to -parallel port 1, for example.
+Backends perform the most important task of all - they send the + filtered print data to the printer.
+CUPS provides backends for printing over parallel, serial, and USB + ports, and over the network via the IPP, JetDirect (AppSocket), and + Line Printer Daemon ("LPD") protocols. Additional backends are + available in network service packages such as the SMB backend included + with the popular SAMBA software.
+Backends are also used to determine the available devices. On startup + each backend is asked for a list of devices it supports, and any + information that is available. This allows the parallel backend to tell + CUPS that an EPSON Stylus Color 600 printer is attached to parallel + port 1, for example.
Printer Drivers
-Printer drivers in CUPS consist of one of more filters specific to a -printer. CUPS includes sample printer drivers for Hewlett-Packard -LaserJet and DeskJet printers and EPSON 9-pin, 24-pin, Stylus Color, -and Stylus Photo printers. While these drivers do not generate optimal -output for the different printer models, they do provide basic printing -and demonstrate how you can write your own printer drivers and -incorporate them into CUPS.
+Printer drivers in CUPS consist of one of more filters specific to a + printer. CUPS includes sample printer drivers for Hewlett-Packard + LaserJet and DeskJet printers and EPSON 9-pin, 24-pin, Stylus Color, + and Stylus Photo printers. While these drivers do not generate optimal + output for the different printer models, they do provide basic printing + and demonstrate how you can write your own printer drivers and + incorporate them into CUPS.
Networking
-Printers and classes on the local system are automatically shared -with other systems on the network. This allows you to setup one system -to print to a printer and use this system as a printer server or spool -host for all of the others. Users may then select a local printer by -name or a remote printer using "name@server".
-CUPS also provides implicit classes, which are collections of -printers and/or classes with the same name. This allows you to setup -multiple servers pointing to the same physical network printer, for -example, so that you aren't relying on a single system for printing. -Because this also works with printer classes, you can setup multiple -servers and printers and never worry about a single point of failure -unless all of the printers and servers go down!
-2 - Building and -Installing CUPS
-This chapter shows how to build and install the Common UNIX Printing -System. If you are installing a binary distribution from the CUPS web -site, proceed to the section titled, Installing a -Binary Distribution.
+Printers and classes on the local system are automatically shared + with other systems on the network. This allows you to setup one system + to print to a printer and use this system as a printer server or spool + host for all of the others. Users may then select a local printer by + name or a remote printer using "name@server".
+CUPS also provides implicit classes, which are collections of + printers and/or classes with the same name. This allows you to setup + multiple servers pointing to the same physical network printer, for + example, so that you aren't relying on a single system for printing. + Because this also works with printer classes, you can setup multiple + servers and printers and never worry about a single point of failure + unless all of the printers and servers go down!
+2 - Building and + Installing CUPS
+This chapter shows how to build and install the Common UNIX Printing + System. If you are installing a binary distribution from the CUPS web + site, proceed to the section titled, Installing a + Binary Distribution.
Installing a Source Distribution
-This section describes how to compile and install CUPS on your -system from the source code.
+This section describes how to compile and install CUPS on your system + from the source code.
Requirements
-You'll need ANSI-compliant C and C++ compilers to build CUPS on your -system. As its name implies, CUPS is designed to run on the UNIX -operating system, however the CUPS interface library and most of the -filters and backends supplied with CUPS should also compile and run -under Microsoft Windows.
-For the image file filters and PostScript RIP, you'll need the JPEG, -PNG, TIFF, and ZLIB libraries. CUPS will build without these, but with -significantly reduced functionality. Easy Software Products maintains a -mirror of the current versions of these libraries at:
+You'll need ANSI-compliant C and C++ compilers to build CUPS on your + system. As its name implies, CUPS is designed to run on the UNIX + operating system, however the CUPS interface library and most of the + filters and backends supplied with CUPS should also compile and run + under Microsoft Windows.
+For the image file filters and PostScript RIP, you'll need the JPEG, + PNG, TIFF, and ZLIB libraries. CUPS will build without these, but with + significantly reduced functionality. Easy Software Products maintains a + mirror of the current versions of these libraries at:
ftp://ftp.easysw.com/pub/libraries-
If you make changes to the man pages you'll need GNU groff or -another nroff-like package. GNU groff is available from:
+If you make changes to the man pages you'll need GNU groff or another + nroff-like package. GNU groff is available from:
ftp://ftp.gnu.org/pub/groff-
The documentation is formatted using the HTMLDOC software. If you -need to make changes you can get the HTMLDOC software from:
+The documentation is formatted using the HTMLDOC software. If you + need to make changes you can get the HTMLDOC software from:
http://www.easysw.com/htmldoc+
Finally, you'll need a make program that understands the
+ include directive - FreeBSD, NetBSD, and OpenBSD
+ developers should use the gmake program.
Compiling CUPS
-CUPS uses GNU autoconf to configure the makefiles and source code -for your system. Type the following command to configure CUPS for your -system:
+CUPS uses GNU autoconf to configure the makefiles and source code for + your system. Type the following command to configure CUPS for your + system:
./configure ENTER-
The default installation will put the CUPS software in the /etc
-, /usr, and /var directories on your system,
-which will overwrite any existing printing commands on your system. Use
-the --prefix option to install the CUPS software in
-another location:
The default installation will put the CUPS software in the /etc
+, /usr, and /var directories on your system, which
+ will overwrite any existing printing commands on your system. Use the
+--prefix option to install the CUPS software in another location:
./configure --prefix=/some/directory ENTER-
If the PNG, JPEG, TIFF, and ZLIB libraries are not installed in a
-system default location (typically /usr/include and
-/usr/lib) you'll need to set the CFLAGS,
-CXXFLAGS, and LDFLAGS environment variables prior
-to running configure:
If the PNG, JPEG, TIFF, and ZLIB libraries are not installed in a
+ system default location (typically /usr/include and
+ /usr/lib) you'll need to set the CFLAGS,
+CXXFLAGS, and LDFLAGS environment variables prior to
+ running configure:
setenv CFLAGS "-I/some/directory" ENTER @@ -526,7 +635,7 @@ to running configure: ./configure ... ENTER-
or:
+or:
CFLAGS="-I/some/directory"; export CFLAGS ENTER @@ -536,30 +645,40 @@ to running configure: ./configure ... ENTER-
To enable support for encryption, you'll also want to add the -"--enable-ssl" option:
+To enable support for encryption, you'll also want to add the + "--enable-ssl" option:
./configure --enable-ssl-
SSL and TLS support require the OpenSSL library, available at:
+SSL and TLS support require the OpenSSL library, available at:
http://www.openssl.org-
Once you have configured things, just type:
+If the OpenSSL headers and libraries are not installed in the
+ standard directories, use the --with-openssl-includes and
+--with-openssl-libs options:
-
+
+./configure --enable-ssl \ + --with-openssl-includes=/foo/bar/include \ + --with-openssl-libs=/foo/bar/lib ++ +
Once you have configured things, just type:
make ENTER-
to build the software. +
to build the software.
Installing the Software
-Use the "install" target to install the software:
+Use the "install" target to install the software:
make install ENTER @@ -568,16 +687,16 @@ to running configure:
WARNING: - Installing CUPS will overwrite your existing printing system. If -you experience difficulties with the CUPS software and need to go back -to your old printing system, you will need to reinstall the old -printing system from your operating system CDs.
+Installing CUPS will overwrite your existing printing system. If you + experience difficulties with the CUPS software and need to go back to + your old printing system, you will need to reinstall the old printing + system from your operating system CDs.
Running the Software
-Once you have installed the software you can start the CUPS server -by typing:
+Once you have installed the software you can start the CUPS server by + typing:
/usr/sbin/cupsd ENTER @@ -586,83 +705,82 @@ by typing:Installing a Binary Distribution
-CUPS comes in a variety of binary distribution formats. Easy -Software Products provides binaries in TAR format with installation and -removal scripts ("portable" distributions), and in RPM and DPKG formats -for Red Hat and Debian-based distributions. Portable distributions are -available for all platforms, while the RPM and DPKG distributions are -only available for Linux. +
CUPS comes in a variety of binary distribution formats. Easy Software + Products provides binaries in TAR format with installation and removal + scripts ("portable" distributions), and in RPM and DPKG formats for Red + Hat and Debian-based distributions. Portable distributions are + available for all platforms, while the RPM and DPKG distributions are + only available for Linux.
WARNING: - Installing CUPS will overwrite your existing printing system. If -you experience difficulties with the CUPS software and need to go back -to your old printing system, you will need to remove the CUPS software -with the provided script and/or reinstall the old printing system from -your operating system CDs.
+Installing CUPS will overwrite your existing printing system. If you + experience difficulties with the CUPS software and need to go back to + your old printing system, you will need to remove the CUPS software + with the provided script and/or reinstall the old printing system from + your operating system CDs.
Installing a Portable Distribution
-To install the CUPS software from a portable distribution you will -need to be logged in as root; doing an
+suis good enough. -Once you are the root user, run the installation script with:To install the CUPS software from a portable distribution you will + need to be logged in as root; doing an
suis good enough. + Once you are the root user, run the installation script with:
./cups.install ENTER-
After asking you a few yes/no questions the CUPS software will be -installed and the scheduler will be started automatically. +
After asking you a few yes/no questions the CUPS software will be + installed and the scheduler will be started automatically.
Installing an RPM Distribution
-To install the CUPS software from an RPM distribution you will need
-to be logged in as root; doing an su is good enough. Once
-you are the root user, run RPM with:
To install the CUPS software from an RPM distribution you will need
+ to be logged in as root; doing an su is good enough. Once
+ you are the root user, run RPM with:
rpm -e lpr rpm -i cups-1.1-linux-M.m.n-intel.rpm ENTER-
After a short delay the CUPS software will be installed and the -scheduler will be started automatically.
+After a short delay the CUPS software will be installed and the + scheduler will be started automatically.
Installing an Debian Distribution
-To install the CUPS software from a Debian distribution you will
-need to be logged in as root; doing an su is good enough.
-Once you are the root user, run dpkg with:
To install the CUPS software from a Debian distribution you will need
+ to be logged in as root; doing an su is good enough. Once
+ you are the root user, run dpkg with:
dpkg -i cups-1.1-linux-M.m.n-intel.deb ENTER-
After a short delay the CUPS software will be installed and the -scheduler will be started automatically.
-3 - Printer Management -
-This chapter describes how to add your first printer and how to -manage your printers.
+After a short delay the CUPS software will be installed and the + scheduler will be started automatically.
+3 - Managing Printers
+This chapter describes how to add your first printer and how to + manage your printers.
The Basics
-Each printer queue has a name associated with it; the printer name -must start with a letter and can contain up to 127 letters, numbers, -and the underscore (_). Case is not significant, e.g. "PRINTER", -"Printer", and "printer" are considered to be the same name.
-Printer queues also have a device associated with them. The device
-can be a parallel port, a network interface, and so forth. Devices
-within CUPS use Uniform Resource Identifiers ("URIs") which are a more
-general form of Uniform Resource Locators ("URLs") that are used in
-your web browser. For example, the first parallel port in Linux usually
-uses a device URI of parallel:/dev/lp1.
+
Each printer queue has a name associated with it; the printer name + must start with any printable character except " ", "/", and "@". It + can contain up to 127 letters, numbers, and the underscore (_). Case is + not significant, e.g. "PRINTER", "Printer", and "printer" are + considered to be the same name.
+Printer queues also have a device associated with them. The device
+ can be a parallel port, a network interface, and so forth. Devices
+ within CUPS use Uniform Resource Identifiers ("URIs") which are a more
+ general form of Uniform Resource Locators ("URLs") that are used in
+ your web browser. For example, the first parallel port in Linux usually
+ uses a device URI of parallel:/dev/lp1.
You can see a complete list of supported devices by running the
-lpinfo(8) command:
lpinfo -v ENTER -file file network socket network http network ipp @@ -674,377 +792,566 @@ direct usb:/dev/usb/lp0 network smb-
The -v option specifies that you want a list of
-available devices. The first word in each line is the type of device
-(direct, file, network, or serial) and is followed by the device URI or
-method name for that device. File devices have device URIs of the form
-file:/directory/filename while network devices use the more
-familiar method://server or method://server/path
- format.
Finally, printer queues usually have a PostScript Printer -Description ("PPD") file associated with them. PPD files describe the -capabilities of each printer, the page sizes supported, etc., and are -used for PostScript and non-PostScript printers. CUPS includes PPD -files for HP LaserJet, HP DeskJet, EPSON 9-pin, EPSON 24-pin, and EPSON -Stylus printers.
+The -v option specifies that you want a list of
+ available devices. The first word in each line is the type of device
+ (direct, file, network, or serial) and is followed by the device URI or
+ method name for that device. File devices have device URIs of the form
+file:/directory/filename while network devices use the more
+ familiar method://server or method://server/path
+ format.
Finally, printer queues usually have a PostScript Printer Description + ("PPD") file associated with them. PPD files describe the capabilities + of each printer, the page sizes supported, etc., and are used for + PostScript and non-PostScript printers. CUPS includes PPD files for HP + LaserJet, HP DeskJet, EPSON 9-pin, EPSON 24-pin, and EPSON Stylus + printers.
Adding Your First Printer
-CUPS provides two methods for adding printers: a command-line
-program called lpadmin(8) and a Web interface. The
-lpadmin command allows you to perform most printer
-administration tasks from the command-line and is located in
-/usr/sbin. The Web interface is located at:
CUPS provides two methods for adding printers: a command-line program
+ called lpadmin(8) and a Web interface. The lpadmin
+ command allows you to perform most printer administration tasks from
+ the command-line and is located in /usr/sbin. The Web
+ interface is located at:
http://localhost:631/admin-
and steps you through printer configuration. If you don't like -command-line interfaces, try the Web interface - instead.
+and steps you through printer configuration. If you don't like + command-line interfaces, try the Web interface + instead.
Adding Your First Printer from the Command-Line
-Run the lpadmin command with the -p option
-to add a printer to CUPS:
Run the lpadmin command with the -p option
+ to add a printer to CUPS:
/usr/sbin/lpadmin -p printer -E -v device -m ppd ENTER-
For an HP DeskJet printer connected to the parallel port this would -look like:
+For a HP DeskJet printer connected to the parallel port this would + look like:
/usr/sbin/lpadmin -p DeskJet -E -v parallel:/dev/lp1 -m deskjet.ppd ENTER-
Similarly, an HP LaserJet printer using a JetDirect network -interface at IP address 11.22.33.44 would be added with the command:
+Similarly, a HP LaserJet printer using a JetDirect network interface + at IP address 11.22.33.44 would be added with the command:
/usr/sbin/lpadmin -p LaserJet -E -v socket://11.22.33.44 -m laserjet.ppd ENTER
As you can see, deskjet.ppd and laserjet.ppd
- are the PPD files for the HP DeskJet and HP LaserJet drivers included
-with CUPS. You'll find a complete list of PPD files and the printers
-they will work with in Appendix C, "Printer
-Drivers".
For a dot matrix printer connected to the serial port, this might + look like:
+-
+
+/usr/sbin/lpadmin -p DotMatrix -E -m epson9.ppd \ + -v serial:/dev/ttyS0?baud=9600+size=8+parity=none+flow=soft ENTER ++ +
Here you specify the serial port (e.g. S0,S1, d0, d1), baud rate + (e.g. 9600, 19200, 38400, 115200, etc.), number of bits, parity, and + flow control. If you do not need flow control, delete the "+flow=soft" + portion.
Adding Your First Printer from the Web
-The CUPS web server provides a user-friendly "wizard" interface for -adding your printers. Rather than figuring out which device URI and PPD -file to use, you can instead click on the appropriate listings and fill -in some simple information. Enter the following URL in your web browser -to begin:
+The CUPS web server provides a user-friendly "wizard" interface for + adding your printers. Rather than figuring out which device URI and PPD + file to use, you can instead click on the appropriate listings and fill + in some simple information. Enter the following URL in your web browser + to begin:
http://localhost:631/admin-
Click on the Add Printer button to add a printer.
+Click on the Add Printer button to add a printer.
Managing Printers from the Command-Line
-The lpadmin command enables you to perform most printer
-administration tasks from the command-line. You'll find lpadmin
- in the /usr/sbin directory.
The lpadmin command enables you to perform most printer
+ administration tasks from the command-line. You'll find lpadmin
+ in the /usr/sbin directory.
Adding and Modifying Printers
-Run the lpadmin command with the -p option
-to add or modify a printer:
Run the lpadmin command with the -p option
+ to add or modify a printer:
/usr/sbin/lpadmin -p printer options ENTER-
The options arguments can be any of the following:
+The options arguments can be any of the following:
- -c class -
- Adds the named printer to printer class class. If the -class does not exist then it is created. -
- -i interface -
- Copies the named interface script to the printer. - Interface scripts are used by System V printer drivers. Since all -filtering is disabled when using an interface script, scripts - generally should not be used unless there is no other driver for a -printer. -
- -m model -
- Specifies a standard printer driver which is usually a PPD file. A
-list of all available models can be displayed using the
lpinfo- command with the-moption. A list of printer drivers -included with CUPS can be found in Appendix -C, "Printer Drivers".
- - -r class -
- Removes the named printer from printer class class. If the -resulting class becomes empty then it is removed. -
- -v device-uri -
- Sets the device for communicating with the printer. If a job is -currently printing on the named printer then the job will be restarted -and sent to the new device. -
- -D info -
- Provides a textual description of the printer, e.g. "John's -Personal Printer". -
- -E -
- Enables the printer and accepts job. This option is equivalent to
-running the
enable(1)andaccept(8)commands -on the printer.
- - -L location -
- Provides a textual location for the printer, e.g. "Computer Lab -5". -
- -P ppd-file -
- Specifies a local PPD file for the printer driver. +
- -c class +
- Adds the named printer to printer class class. If the + class does not exist then it is created. +
- -i interface +
- Copies the named interface script to the printer. + Interface scripts are used by System V printer drivers. Since all + filtering is disabled when using an interface script, scripts generally + should not be used unless there is no other driver for a printer. +
- -m model +
- Specifies a standard printer driver which is usually a PPD file.
+ PPD's are usually stored under the /usr/share/cups/model/
+ directory structure. A list of all available models can be displayed
+ using the
lpinfocommand with the-moption. + A list of printer drivers included with CUPS can be found in +Appendix C, "Printer Drivers".
+ - -r class +
- Removes the named printer from printer class class. If + the resulting class becomes empty then it is removed. +
- -v device-uri +
- Sets the device for communicating with the printer. If a job is + currently printing on the named printer then the job will be restarted + and sent to the new device. +
- -D info +
- Provides a textual description of the printer, e.g. "John's Personal + Printer". +
- -E +
- Enables the printer and accepts job. This option is equivalent to
+ running the
enable(1)andaccept(8)commands + on the printer.
+ - -L location +
- Provides a textual location for the printer, e.g. "Computer Lab 5". +
- -P ppd-file +
- Specifies a local PPD file for the printer driver.
-
-
Deleting Printers
-Run the lpadmin command with the -x option
-to delete a printer:
Run the lpadmin command with the -x option
+ to delete a printer:
/usr/sbin/lpadmin -x printer ENTER
Setting the Default Printer
-Run the lpadmin command with the -d option
-to set a default printer:
Run the lpadmin command with the -d option
+ to set a default printer:
/usr/sbin/lpadmin -d printer ENTER
The default printer can be overridden by the user using the
-lpoptions(1) command.
Starting and Stopping Printers
-The enable and disable commands start and
-stop printer queues, respectively:
The enable and disable commands start and
+ stop printer queues, respectively:
/usr/bin/enable printer ENTER /usr/bin/disable printer ENTER-
Printers that are disabled may still accept jobs for printing, but -won't actually print any files until they are restarted. This is useful -if the printer malfunctions and you need time to correct the problem. -Any queued jobs are printed after the printer is enabled (started).
+Printers that are disabled may still accept jobs for printing, but + won't actually print any files until they are restarted. This is useful + if the printer malfunctions and you need time to correct the problem. + Any queued jobs are printed after the printer is enabled (started).
Accepting and Rejecting Print Jobs
-The accept and reject commands accept and
-reject print jobs for the named printer, respectively:
The accept and reject commands accept and
+ reject print jobs for the named printer, respectively:
/usr/sbin/accept printer ENTER /usr/sbin/reject printer ENTER-
As noted above, a printer can be stopped but accepting new print -jobs. A printer can also be rejecting new print jobs while it finishes -those that have been queued. This is useful for when you must perform -maintenance on the printer and will not have it available to users for -a long period of time.
+As noted above, a printer can be stopped but accepting new print + jobs. A printer can also be rejecting new print jobs while it finishes + those that have been queued. This is useful for when you must perform + maintenance on the printer and will not have it available to users for + a long period of time.
+Setting Quotas on a Printer
+CUPS supports page and size-based quotas for each printer. The quotas + are tracked individually for each user, but a single set of limits + applies to all users for a partiuclar printer. For example, you can + limit every user to 5 pages per day on an expensive printer, but you + cannot limit every user except Johnny.
+The job-k-limit, job-page-limit, and job-quota-peiod + options determine whether and how quotas are enforced for a printer. + The job-quota-period option determines the time interval for + quota tracking. The interval is expressed in seconds, so a day is + 86,400, a week is 604,800 and a month is 2,592,000 seconds. The + job-k-limit option specifies the job size limit in killobytes. The + job-page-limit option specifies the number of pages limit.
+For quotas to be enforced, the period and at least one of the limits + must be set to a non-zero value. The following options will enable + quotas:
+-
+
+/usr/sbin/lpadmin -p printer -o job-quota-period=604800 \ + -o job-k-limit=1024 ENTER +/usr/sbin/lpadmin -p printer -o job-quota-period=604800 \ + -o job-page-limit=100 ENTER ++ +
Or, you can combine all three options on the same line.
+Restricting User Access to a Printer
+The -u option of the lpadmin command
+ controls which users can print to a printer. The default configuration
+ allows all users to print to a printer:
-
+
+/usr/sbin/lpadmin -p printer -u allow:all ENTER ++ +
CUPS supports allow and deny lists so that you can specify a list of + users who are allowed to print or not allowed to print. Along with your + list of users, you can specify whether they are allowed or not allowed + to use the printer:
+-
+
+/usr/sbin/lpadmin -p printer -u allow:peter,paul,mary ENTER ++ +
This command allows peter, paul, and mary to print to the named + printer, but all other users cannot print. The command:
+-
+
+/usr/sbin/lpadmin -p printer -u deny:peter,paul,mary ENTER ++ +
has the opposite effect. All users except peter, paul, and mary will + be able to print to the named printer.
+You can control access by UNIX groups as well by placing an "@" + character before each group name. The command:
+-
+
+/usr/sbin/lpadmin -p printer -u allow:peter,paul,mary,@printgods ENTER ++ +
allows the users peter, paul, and mary to print, as well as any user + in the printgods group to print. +
| NOTE:
+ The allow and deny options are not cummulative. That + is, you must provide the complete list of users to allow or deny each + time. +Also, CUPS only maintains one list of users - the list can allow or + deny users from printing. If you specify an allow list and then specify + a deny list, the deny list will replace the allow list - only one list + is active at any time. + |
Managing Printers from the Web
-The Web interface is located at:
+The Web interface is located at:
http://localhost:631/admin-
From there you can perform all printer management tasks with a few -simple mouse clicks.
+From there you can perform all printer management tasks with a few + simple mouse clicks.
4 - Printer Classes
-This chapter describes what printer classes are and how to manage -them.
+This chapter describes what printer classes are and how to manage + them.
The Basics
-CUPS provides collections of printers called printer classes. -Jobs sent to a class are forwarded to the first available printer in -the class. Classes can themselves be members of other classes, so it is -possible for you to define very large, distributed printer classes for -high-availability printing.
-CUPS also supports implicit classes. Implicit classes work -just like printer classes, but they are created automatically based -upon the available printers and classes on the network. This allows you -to setup multiple print servers with identical printer configurations -and have the client machines send their print jobs to the first -available server. If one or more servers go down, the jobs are -automatically redirected to the servers that are running, providing -fail-safe printing.
+CUPS provides collections of printers called printer classes. + Jobs sent to a class are forwarded to the first available printer in + the class. Classes can themselves be members of other classes, so it is + possible for you to define very large, distributed printer classes for + high-availability printing.
+CUPS also supports implicit classes. Implicit classes work + just like printer classes, but they are created automatically based + upon the available printers and classes on the network. This allows you + to setup multiple print servers with identical printer configurations + and have the client machines send their print jobs to the first + available server. If one or more servers go down, the jobs are + automatically redirected to the servers that are running, providing + fail-safe printing.
Managing Printer Classes from the Command-Line
Run the lpadmin command with the -p and
--c options to add a printer to a class:
/usr/sbin/lpadmin -p printer -c class ENTER-
The class is created automatically if it doesn't exist. To
-remove a printer from a class use the -r option:
The class is created automatically if it doesn't exist. To
+ remove a printer from a class use the -r option:
/usr/sbin/lpadmin -p printer -r class ENTER-
To remove the entire class just use the -x option:
To remove the entire class just use the -x option:
/usr/sbin/lpadmin -x class ENTER
Managing Printer Classes from the Web Interface
-The Web interface is located at:
+The Web interface is located at:
http://localhost:631/admin-
The Add Class and Modify Class interfaces -provide a list of available printers; click on the printers of interest -to add them to the class.
+The Add Class and Modify Class interfaces + provide a list of available printers; click on the printers of interest + to add them to the class.
Implicit Classes
-A noted earlier, implicit classes are created automatically from the
-available network printers and classes. To disable this functionality,
-set the ImplicitClasses
- directive to Off in the cupsd.conf file. You
-will find more information on doing this in
-Chapter 6, "Printing System Management".
A noted earlier, implicit classes are created automatically from the
+ available network printers and classes. To disable this functionality,
+ set the ImplicitClasses
+ directive to Off in the cupsd.conf file. You
+ will find more information on doing this in
+Chapter 6, "Printing System Management".
5 - Client Setup
-This chapter discusses several ways to configure CUPS clients for -printing.
+This chapter discusses several ways to configure CUPS clients for + printing.
The Basics
-A client is any machine that sends print jobs to another machine for -final printing. Clients can also be servers if they communicate -directly with any printers of their own.
-CUPS supports several methods of configuring client machines:
+A client is any machine that sends print jobs to another machine for + final printing. Clients can also be servers if they communicate + directly with any printers of their own.
+CUPS supports several methods of configuring client machines:
- Manual configuration of print queues.
- Specifying a single server for printing.
- Automatic configuration of print queues.
- Specifying multiple servers for printing. +
- Relaying printers to other clients.
Manual Configuration of Print Queues
-The most tedious method of configuring client machines is to
-configure each remote queue by hand using the lpadmin
- command:
The most tedious method of configuring client machines is to
+ configure each remote queue by hand using the lpadmin
+ command:
lpadmin -p printer -E -v ipp://server/printers/printer ENTER-
The printer name is the name of the printer on the
-server machine. The server name is the hostname or IP
-address of the server machine. Repeat the lpadmin command
-for each remote printer you wish to use.
The printer name is the name of the printer on the
+ server machine. The server name is the hostname or IP
+ address of the server machine. Repeat the lpadmin command
+ for each remote printer you wish to use.
| NOTE:
+ Manual configuration of print queues is not recommended for large + numbers of client machines because of the administration nightmare it + creates. For busy networks, consider subnetting groups of clients and + polling and relaying printer information instead. + |
Specifying a Single Server for Printing
-CUPS can be configured to run without a local spooler and send all -jobs to a single server. However, if that server goes down then all -printing will be disabled. Use this configuration only as absolutely -needed.
-The default server is normally "localhost". To override the default -server create a file named /etc/cups/client.conf and add a -line reading:
+CUPS can be configured to run without a local spooler and send all + jobs to a single server. However, if that server goes down then all + printing will be disabled. Use this configuration only as absolutely + needed.
+The default server is normally "localhost". To override the default + server create a file named /etc/cups/client.conf and add a + line reading:
ServerName server-
to the file. The server name can be the hostname or IP -address of the default server.
-The default server can also be customized on a per-user basis. To -set a user-specific server create a file named ~/.cupsrc and -add a line reading:
+to the file. The server name can be the hostname or IP + address of the default server.
+The default server can also be customized on a per-user basis. To set + a user-specific server create a file named ~/.cupsrc and add + a line reading:
ServerName server-
to the file. The server name can be the hostname or IP -address of the default server.
+to the file. The server name can be the hostname or IP + address of the default server.
Automatic Configuration of Print Queues
-CUPS supports automatic client configuration of printers on the same -subnet. To configure printers on the same subnet, do nothing. -Each client should see the available printers within 30 seconds -automatically. The printer and class lists are updated automatically as -printers and servers are added or removed.
+CUPS supports automatic client configuration of printers on the same + subnet. To configure printers on the same subnet, do nothing. + Each client should see the available printers within 30 seconds + automatically. The printer and class lists are updated automatically as + printers and servers are added or removed.
If you want to see printers on other subnets as well, use the
-BrowsePoll directive as described next.
BrowsePoll directive as described next.
+| NOTE:
+ The Use the |
Specifying Multiple Servers for Printing
-If you have CUPS servers on different subnets, then you should -configure CUPS to poll those servers. Polling provides the benefits of -automatic configuration without significant configuration on the -clients, and multiple clients on the same subnet can share the same -configuration information.
+If you have CUPS servers on different subnets, then you should + configure CUPS to poll those servers. Polling provides the benefits of + automatic configuration without significant configuration on the + clients, and multiple clients on the same subnet can share the same + configuration information.
Polling is enabled by specifying one or more
-BrowsePoll directives in the /etc/cups/cupsd.conf
- file. For information on making these changes, see
-Chapter 6, "Printing System Management".
6 - Printing System -Management
-This chapter shows how you can configure the CUPS server.
+BrowsePoll directives in the /etc/cups/cupsd.conf + file. For information on making these changes, see +Chapter 6, "Printing System Management". +Multiple BrowsePoll lines can
+ be used to poll multiple CUPS servers. To limit the amount of polling
+ you do from client machines, you can have only one of the clients do
+ the polling and relay that information to the others on the same subnet
+ (described next).
Relaying Printers to Other Clients
+When you have clients and servers spread across multiple subnets, the
+ polling method is inefficient. CUPS provides a
+BrowseRelay directive that enables a single client to relay
+ (broadcast) the polled printer information to the local subnet.
For example, Server A and Server B are on subnet 1 and subnet 2, + while the clients are on subnet 3. To provide printers to all of the + clients in subnet 3, client C will be configured with the following + directives in /etc/cups/cupsd.conf:
+-
+
+# Poll the two servers + +BrowsePoll ServerA +BrowsePoll ServerB + + +# Relay the printers to the local subnet + +BrowseRelay 127.0.0.1 192.168.3.255 ++ +
The BrowseRelay line
+ specifies a source address and mask. Any browse packets coming from a
+ matching address wil be sent to the given broadcast address. In this
+ case, we want the packets from the local machine (127.0.0.1) relayed to
+ the other clients.
As printers are found using polling, they are relayed from client C + to the rest of the clients through a broadcast on subnet 3. The rest of + the clients can use the standard cupsd.conf configuration.
+The BrowseRelay directive can
+ also be used to relay browsing packets from one network interface to
+ another. For example, if client C in the previous example had network
+ interfaces attaches to both subnet 1 and subnet 2, it could use the
+BrowseRelay directive exclusively:
-
+
+# Relay the printers from subnet 1 and 2 to subnet 3 + +BrowseRelay 192.168.1 192.168.3.255 +BrowseRelay 192.168.2 192.168.3.255 ++ + + +
Load Balancing and Failsafe Operation
+When using server polling or broadcasting, CUPS clients can + automatically merge identical printers on multiple servers into a + single implicit class queue. Clients assume that printers with + the same name on multiple servers are in fact the same printer or type + of printer being served by multiple machines.
+If you have two printers, LaserJet@ServerA and LaserJet@ServerB, a
+ third implicit class called LaserJet will be created
+ automatically on the client that refers to both printers. If the client
+ also has a local printer with the name LaserJet and the
+ImplicitAnyClasses directive is enabled, then an
+ implicit class named AnyLaserJet will be created instead.
+ Otherwise, the local printer will prevent the creation of an implicit
+ class, since CUPS will assume that the local printer will always be
+ more available than a remote one.
The client will alternate between servers and automatically stop + sending jobs to a server if it goes down, providing a load-balancing + effect and fail-safe operation with automatic switchover.
+| NOTE:
+ Note that implicit classes ( |
6 - Printing System + Management
+This chapter shows how you can configure the CUPS server.
The Basics
-Several text files are used to configure CUPS. All of the server -configuration files are located in the /etc/cups directory:
+Several text files are used to configure CUPS. All of the server + configuration files are located in the /etc/cups directory:
- classes.conf -
- This file contains information on each printer class. Normally you
-manipulate this file using the
lpadmincommand or the Web -interface. -
+ - classes.conf +
- This file contains information on each printer class. Normally you
+ manipulate this file using the
lpadmincommand or the Web + interface. +
- - client.conf -
- This file provides the default server name for client machines.
-See Chapter 5, "Client Setup" for more
-information.
-
+ - client.conf +
- This file provides the default server name for client machines. See Chapter 5, "Client Setup" for more information.
+
- - cupsd.conf -
- This file controls how the CUPS server (/usr/sbin/cupsd
-) operates and is normally edited by hand.
-
+ - cupsd.conf +
- This file controls how the CUPS server (/usr/sbin/cupsd)
+ operates and is normally edited by hand.
+
- - mime.convs -
- This file contains a list of standard file conversion filters and
-their costs. You normally do not edit this file.
-
+ - mime.convs +
- This file contains a list of standard file conversion filters and
+ their costs. You normally do not edit this file.
+
- - mime.types -
- This file contains a list of standard file formats and how to +
- mime.types +
- This file contains a list of standard file formats and how to
recognize them. You normally do not edit this file.
-
+
- - printers.conf -
- This file contains information on each printer. Normally you
-manipulate this file using the
lpadmincommand or the Web -Interface. -
+ - printers.conf +
- This file contains information on each printer. Normally you
+ manipulate this file using the
lpadmincommand or the Web + Interface. +
-
-
-
Restarting the CUPS Server
-Once you have made a change to a configuration file you need to
-restart the CUPS server by sending it a HUP signal or
-using the supplied initialization script. The CUPS distributions
-install the script in the init.d directory with the name
-cups. The location varies based upon the operating system:
Once you have made a change to a configuration file you need to
+ restart the CUPS server by sending it a HUP signal or
+ using the supplied initialization script. The CUPS distributions
+ install the script in the init.d directory with the name
+ cups. The location varies based upon the operating system:
+/etc/software/init.d/cups restart ENTER /etc/rc.d/init.d/cups restart ENTER /etc/init.d/cups restart ENTER /sbin/init.d/cups restart ENTER
Changing the Server Configuration
-The /etc/cups/cupsd.conf file contains configuration -directives that control how the server functions. Each directive is -listed on a line by itself followed by its value. Comments are -introduced using the number sign ("#") character at the beginning of a -line. Since the server configuration file consists of plain text, you -can use your favorite text editor to make changes to it. +
The /etc/cups/cupsd.conf file contains configuration + directives that control how the server functions. Each directive is + listed on a line by itself followed by its value. Comments are + introduced using the number sign ("#") character at the beginning of a + line. Since the server configuration file consists of plain text, you + can use your favorite text editor to make changes to it.
Server Directives
-The cupsd.conf file contains many directives that -determine how the server operates:
+The cupsd.conf file contains many directives that + determine how the server operates:
BrowseOrderBrowsePollBrowsePort
+BrowseProtocolsBrowseRelayBrowseShortNamesBrowseTimeoutBrowsingClassification
+ClassifyOverride
+ConfigFilePermDataDirDefaultCharsetDefaultLanguageDenyDocumentRoot
-EncryptionErrorLog
+FaxRetryInterval
+FaxRetryLimit
+FileDeviceFilterLimit
+FilterNiceFontPathGroup
+HideImplicitMembersHostNameLookups
+ImplicitAnyClassesImplicitClasses
+IncludeKeepAliveTimeoutKeepAliveLimit
@@ -1086,25 +1403,31 @@ determine how the server operates:
LimitRequestBodyListenLocation
+LogFilePermLogLevelMaxClients
+MaxClientsPerHost
+MaxCopiesMaxJobsMaxJobsPerPrinterMaxJobsPerUserMaxLogSizeMaxRequestSizeOrder
+PageLog
-PortPreserveJobFilesPreserveJobHistoryPrintcapPrintcapFormat
+PrintcapGUI
+ReloadTimeoutRemoteRootRequestRootRequireRIPCache
+RootCertDurationRunAsUserSatisfyServerAdmin
@@ -1113,6 +1436,7 @@ determine how the server operates:
ServerKeyServerNameServerRoot
+ServerTokensSSLListenSSLPortSystemGroup
@@ -1135,16 +1459,16 @@ AccessLog syslog
Anonymous- No authentication should be performed - (default.)
-User- A valid username and password is required.
-System- A valid username and password is required, -and the username must belong to the "sys" group; this can be changed -using theSystemGroup- directive.
-Group- A valid username and password is required, -and the username must belong to the group named by the-AuthGroupNamedirective.
+Anonymous- No authentication should be performed + (default.)
+User- A valid username and password is required.
+System- A valid username and password is required, and + the username must belong to the "sys" group; this can be changed using + theSystemGroupdirective.
+Group- A valid username and password is required, and + the username must belong to the group named by theAuthGroupName+ directive.None- No authentication should be performed - (default.)
-Basic- Basic authentication should be performed -using the UNIX password and group files.
-Digest- Digest authentication should be performed -using the /etc/cups/passwd.md5 file.
-None- No authentication should be performed (default.)
+Basic- Basic authentication should be performed using + the UNIX password and group files.
+Digest- Digest authentication should be performed + using the /etc/cups/passwd.md5 file.
+BasicDigest- Basic authentication should be performed + using the /etc/cups/passwd.md5 file.
+allow,deny- Browse packets are accepted unless - specifically denied.
-deny,allow- Browse packets are rejected unless - specifically allowed.
-allow,deny- Browse packets are accepted unless + specifically denied.
+deny,allow- Browse packets are rejected unless + specifically allowed.
+none- Log nothing.
-emerg- Log emergency conditions that prevent the - server from running.
-alert- Log alerts that must be handled immediately.
-crit- Log critical errors that don't prevent the -server from running.
-error- Log general errors.
-warn- Log errors and warnings.
-notice- Log temporary error conditions.
-info- Log all requests and state changes (default).
-debug- Log basic debugging information.
-debug2- Log all debugging information.
+none- Log nothing.
+emerg- Log emergency conditions that prevent the + server from running.
+alert- Log alerts that must be handled immediately.
+crit- Log critical errors that don't prevent the + server from running.
+error- Log general errors.
+warn- Log errors and warnings.
+notice- Log temporary error conditions.
+info- Log all requests and state changes (default).
+debug- Log basic debugging information.
+debug2- Log all debugging information.Allow,Deny- Allow requests from all systems except - for those listed in aDenydirective.
-Deny,Allow- Allow requests only from those listed in -anAllowdirective.
+Allow,Deny- Allow requests from all systems except + for those listed in aDenydirective.
+Deny,Allow- Allow requests only from those listed in + anAllowdirective.Encryption
+ServerName
+Accepting
+AllowUser
+DefaultPrinter
+DenyUser
+DeviceURI
+Info
+JobSheets
+KLimit
+Location
+PageLimit
+Printer
+QuotaPeriod
+State
+StateMessage
+none- Do not produce a banner page.
+classified- A banner page with a "classified" label at + the top and bottom.
+confidential- A banner page with a "confidential" + label at the top and bottom.
+secret- A banner page with a "secret" label at the top + and bottom.
+standard- A banner page with no label at the top and + bottom.
+topsecret- A banner page with a "top secret" label at + the top and bottom.
+unclassified- A banner page with an "unclassified" + label at the top and bottom.
+- Connected to host_name... +
- Connecting to printer_queue on port port_number +... +
- Network host host_name is busy; will retry in 30 + seconds... +
- Printer busy; will retry in 10 seconds... +
- Printer is busy; retrying print job... +
- Print file accepted - job ID id_number. +
- Ready to print. +
- Waiting for job to complete +
Accepting
+AllowUser
+Class
+DefaultClass
+DenyUser
+Info
+JobSheets
+KLimit
+Location
+PageLimit
+Printer
+QuotaPeriod
+State
+StateMessage
+none- Do not produce a banner page.
+classified- A banner page with a "classified" label at + the top and bottom.
+confidential- A banner page with a "confidential" + label at the top and bottom.
+secret- A banner page with a "secret" label at the top + and bottom.
+standard- A banner page with no label at the top and + bottom.
+topsecret- A banner page with a "top secret" label at + the top and bottom.
+unclassified- A banner page with an "unclassified" + label at the top and bottom.
+- Connected to host_name... +
- Connecting to class_queue on port port_number +... +
- Network host host_name is busy; will retry in 30 + seconds... +
- Printer busy; will retry in 10 seconds... +
- Printer is busy; retrying print job... +
- Print file accepted - job ID id_number. +
- Ready to print. +
- Waiting for job to complete +
E- An error occurred.
-W- The server was unable to perform some action.
-I- Informational message.
-D- Debugging message.
+E- An error occurred.
+W- The server was unable to perform some action.
+I- Informational message.
+D- Debugging message.( expr )- Parenthesis for expression grouping
-+- Logical AND
-,or whitespace - Logical OR
-!- Logical NOT
-match("pattern")- Pattern match on filename
-extension- Pattern match on "*.extension"
-ascii(offset,length)- True if bytes are valid - printable ASCII (CR, NL, TAB, BS, 32-126)
-printable(offset,length)- True if bytes are - printable 8-bit chars (CR, NL, TAB, BS, 32-126, 160-254)
-string(offset,"string")- True if bytes are identical -to string
-contains(offset,range,"string")- True if the range -of bytes contains the string
-char(offset,value)- True if byte is identical
-short(offset,value)- True if 16-bit integer is -identical (network or "big-endian" byte order)
-int(offset,value)- True if 32-bit integer is - identical (network or "big-endian" byte order)
-locale("string")- True if current locale matches -string
-( expr )- Parenthesis for expression grouping
++- Logical AND
+,or whitespace - Logical OR
+!- Logical NOT
+match("pattern")- Pattern match on filename
+extension- Pattern match on "*.extension"
+ascii(offset,length)- True if bytes are valid + printable ASCII (CR, NL, TAB, BS, 32-126)
+printable(offset,length)- True if bytes are printable + 8-bit chars (CR, NL, TAB, BS, 32-126, 160-254)
+string(offset,"string")- True if bytes are identical + to string
+istring(offset,"string")- True if bytes are identical + to string after reducing both strings to lowercase
+contains(offset,range,"string")- True if the range of + bytes contains the string
+char(offset,value)- True if byte is identical
+short(offset,value)- True if 16-bit integer is + identical (network or "big-endian" byte order)
+int(offset,value)- True if 32-bit integer is identical + (network or "big-endian" byte order)
+locale("string")- True if current locale matches + string
+- Use the CUPS software at no charge. -
- Distribute verbatim copies of the software in source or binary -form. -
- Sell verbatim copies of the software for a media fee, or sell -support for the software. -
- Distribute or sell printer drivers and filters that use CUPS so -long as source code is made available under the GPL. -
- Use the CUPS software at no charge. +
- Distribute verbatim copies of the software in source or binary form. +
- Sell verbatim copies of the software for a media fee, or sell + support for the software. +
- Distribute or sell printer drivers and filters that use CUPS so long + as source code is made available under the GPL. +
- Apple Operating System Development License Exception;
+
-
+
- Software that is developed by any person or entity for an Apple + Operating System ("Apple OS-Developed Software"), including but not + limited to Apple and third party printer drivers, filters, and backends + for an Apple Operating System, that is linked to the CUPS imaging + library or based on any sample filters or backends provided with CUPS + shall not be considered to be a derivative work or collective work + based on the CUPS program and is exempt from the mandatory source code + release clauses of the GNU GPL. You may therefore distribute linked + combinations of the CUPS imaging library with Apple OS-Developed + Software without releasing the source code of the Apple OS-Developed + Software. You may also use sample filters and backends provided with + CUPS to develop Apple OS-Developed Software without releasing the + source code of the Apple OS-Developed Software. +
- An Apple Operating System means any operating system software + developed and/or marketed by Apple Computer, Inc., including but not + limited to all existing releases and versions of Apple's Darwin, Mac OS + X, and Mac OS X Server products and all follow-on releases and future + versions thereof. +
- This exception is only available for Apple OS-Developed Software and + does not apply to software that is distributed for use on other + operating systems. +
- All CUPS software that falls under this license exception have the
+ following text at the top of each source file:
This file is + subject to the Apple OS-Developed Software exception.
+
+ - OpenSSL Toolkit License Exception;
+
-
+
- Easy Software Products explicitly allows the compilation and + distribution of the CUPS software with the OpenSSL Toolkit. +
+ - This License applies to any program or other work which contains a -notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The "Program", below, -refers to any such program or work, and a "work based on the Program" -means either the Program or any derivative work under copyright law: -that is to say, a work containing the Program or a portion of it, -either verbatim or with modifications and/or translated into another -language. (Hereinafter, translation is included without limitation in -the term "modification".) Each licensee is addressed as "you". -
- You may copy and distribute verbatim copies of the Program's source -code as you receive it, in any medium, provided that you conspicuously -and appropriately publish on each copy an appropriate copyright notice -and disclaimer of warranty; keep intact all the notices that refer to -this License and to the absence of any warranty; and give any other -recipients of the Program a copy of this License along with the -Program. -
- You may modify your copy or copies of the Program or any portion of -it, thus forming a work based on the Program, and copy and distribute -such modifications or work under the terms of Section 1 above, provided -that you also meet all of these conditions: +
- This License applies to any program or other work which contains a
+ notice placed by the copyright holder saying it may be distributed
+ under the terms of this General Public License. The "Program", below,
+ refers to any such program or work, and a "work based on the Program"
+ means either the Program or any derivative work under copyright law:
+ that is to say, a work containing the Program or a portion of it,
+ either verbatim or with modifications and/or translated into another
+ language. (Hereinafter, translation is included without limitation in
+ the term "modification".) Each licensee is addressed as "you".
+
Activities other than copying, distribution and modification are not + covered by this License; they are outside its scope. The act of running + the Program is not restricted, and the output from the Program is + covered only if its contents constitute a work based on the Program + (independent of having been made by running the Program). Whether that + is true depends on what the Program does.
+
+ - You may copy and distribute verbatim copies of the Program's source
+ code as you receive it, in any medium, provided that you conspicuously
+ and appropriately publish on each copy an appropriate copyright notice
+ and disclaimer of warranty; keep intact all the notices that refer to
+ this License and to the absence of any warranty; and give any other
+ recipients of the Program a copy of this License along with the
+ Program.
+
You may charge a fee for the physical act of transferring a copy, and + you may at your option offer warranty protection in exchange for a fee.
+
+ - You may modify your copy or copies of the Program or any portion of
+ it, thus forming a work based on the Program, and copy and distribute
+ such modifications or work under the terms of Section 1 above, provided
+ that you also meet all of these conditions:
-
-
- You must cause the modified files to carry prominent notices -stating that you changed the files and the date of any change. -
- You must cause any work that you distribute or publish, that in -whole or in part contains or is derived from the Program or any part -thereof, to be licensed as a whole at no charge to all third parties -under the terms of this License. -
- if the modified program normally reads commands interactively when -run, you must cause it, when started running for such interactive use -in the most ordinary way, to print or display an announcement including -an appropriate copyright notice and a notice that there is no warranty -(or else, saying that you provide a warranty) and that users may -redistribute the program under these conditions, and telling the user -how to view a copy of this License. (Exception: if the Program itself -is interactive but does not normally print such an announcement, your -work based on the Program is not required to print an announcement.) +
- You must cause the modified files to carry prominent notices stating + that you changed the files and the date of any change. +
- You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any part + thereof, to be licensed as a whole at no charge to all third parties + under the terms of this License. +
- if the modified program normally reads commands interactively when + run, you must cause it, when started running for such interactive use + in the most ordinary way, to print or display an announcement including + an appropriate copyright notice and a notice that there is no warranty + (or else, saying that you provide a warranty) and that users may + redistribute the program under these conditions, and telling the user + how to view a copy of this License. (Exception: if the Program itself + is interactive but does not normally print such an announcement, your + work based on the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If + identifiable sections of that work are not derived from the Program, + and can be reasonably considered independent and separate works in + themselves, then this License, and its terms, do not apply to those + sections when you distribute them as separate works. But when you + distribute the same sections as part of a whole which is a work based + on the Program, the distribution of the whole must be on the terms of + this License, whose permissions for other licensees extend to the + entire whole, and thus to each and every part regardless of who wrote + it.
+Thus, it is not the intent of this section to claim rights or contest + your rights to work written entirely by you; rather, the intent is to + exercise the right to control the distribution of derivative or + collective works based on the Program.
+In addition, mere aggregation of another work not based on the + Program with the Program (or with a work based on the Program) on a + volume of a storage or distribution medium does not bring the other + work under the scope of this License.
- - You may copy and distribute the Program (or a work based on it, -under Section 2) in object code or executable form under the terms of -Sections 1 and 2 above provided that you also do one of the following: +
- You may copy and distribute the Program (or a work based on it,
+ under Section 2) in object code or executable form under the terms of
+ Sections 1 and 2 above provided that you also do one of the following:
-
-
- Accompany it with the complete corresponding machine-readable -source code, which must be distributed under the terms of Sections 1 -and 2 above on a medium customarily used for software interchange; or, -
- Accompany it with a written offer, valid for at least three years, -to give any third party, for a charge no more than your cost of -physically performing source distribution, a complete machine-readable -copy of the corresponding source code, to be distributed under the -terms of Sections 1 and 2 above on a medium customarily used for -software interchange; or, -
- Accompany it with the information you received as to the offer to -distribute corresponding source code. (This alternative is allowed -only for noncommercial distribution and only if you received the -program in object code or executable form with such an offer, in accord -with Subsection b above.) +
- Accompany it with the complete corresponding machine-readable source + code, which must be distributed under the terms of Sections 1 and 2 + above on a medium customarily used for software interchange; or, +
- Accompany it with a written offer, valid for at least three years, + to give any third party, for a charge no more than your cost of + physically performing source distribution, a complete machine-readable + copy of the corresponding source code, to be distributed under the + terms of Sections 1 and 2 above on a medium customarily used for + software interchange; or, +
- Accompany it with the information you received as to the offer to + distribute corresponding source code. (This alternative is allowed only + for noncommercial distribution and only if you received the program in + object code or executable form with such an offer, in accord with + Subsection b above.)
The source code for a work means the preferred form of the work for + making modifications to it. For an executable work, complete source + code means all the source code for all modules it contains, plus any + associated interface definition files, plus the scripts used to control + compilation and installation of the executable. However, as a special + exception, the source code distributed need not include anything that + is normally distributed (in either source or binary form) with the + major components (compiler, kernel, and so on) of the operating system + on which the executable runs, unless that component itself accompanies + the executable.
+If distribution of executable or object code is made by offering + access to copy from a designated place, then offering equivalent access + to copy the source code from the same place counts as distribution of + the source code, even though third parties are not compelled to copy + the source along with the object code.
+
+ - You may not copy, modify, sublicense, or distribute the Program + except as expressly provided under this License. Any attempt otherwise + to copy, modify, sublicense or distribute the Program is void, and will + automatically terminate your rights under this License. However, + parties who have received copies, or rights, from you under this + License will not have their licenses terminated so long as such parties + remain in full compliance. +
- You are not required to accept this License, since you have not + signed it. However, nothing else grants you permission to modify or + distribute the Program or its derivative works. These actions are + prohibited by law if you do not accept this License. Therefore, by + modifying or distributing the Program (or any work based on the + Program), you indicate your acceptance of this License to do so, and + all its terms and conditions for copying, distributing or modifying the + Program or works based on it. +
- Each time you redistribute the Program (or any work based on the + Program), the recipient automatically receives a license from the + original licensor to copy, distribute or modify the Program subject to + these terms and conditions. You may not impose any further restrictions + on the recipients' exercise of the rights granted herein. You are not + responsible for enforcing compliance by third parties to this License. +
- If, as a consequence of a court judgment or allegation of patent
+ infringement or for any other reason (not limited to patent issues),
+ conditions are imposed on you (whether by court order, agreement or
+ otherwise) that contradict the conditions of this License, they do not
+ excuse you from the conditions of this License. If you cannot
+ distribute so as to satisfy simultaneously your obligations under this
+ License and any other pertinent obligations, then as a consequence you
+ may not distribute the Program at all. For example, if a patent license
+ would not permit royalty-free redistribution of the Program by all
+ those who receive copies directly or indirectly through you, then the
+ only way you could satisfy both it and this License would be to refrain
+ entirely from distribution of the Program.
+
If any portion of this section is held invalid or unenforceable under + any particular circumstance, the balance of the section is intended to + apply and the section as a whole is intended to apply in other + circumstances.
+It is not the purpose of this section to induce you to infringe any + patents or other property right claims or to contest validity of any + such claims; this section has the sole purpose of protecting the + integrity of the free software distribution system, which is + implemented by public license practices. Many people have made generous + contributions to the wide range of software distributed through that + system in reliance on consistent application of that system; it is up + to the author/donor to decide if he or she is willing to distribute + software through any other system and a licensee cannot impose that + choice.
+This section is intended to make thoroughly clear what is believed to + be a consequence of the rest of this License.
- - You may not copy, modify, sublicense, or distribute the Program -except as expressly provided under this License. Any attempt otherwise -to copy, modify, sublicense or distribute the Program is void, and will -automatically terminate your rights under this License. However, -parties who have received copies, or rights, from you under this -License will not have their licenses terminated so long as such parties -remain in full compliance. -
- You are not required to accept this License, since you have not -signed it. However, nothing else grants you permission to modify or -distribute the Program or its derivative works. These actions are -prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Program (or any work based on the -Program), you indicate your acceptance of this License to do so, and -all its terms and conditions for copying, distributing or modifying the -Program or works based on it. -
- Each time you redistribute the Program (or any work based on the -Program), the recipient automatically receives a license from the -original licensor to copy, distribute or modify the Program subject to -these terms and conditions. You may not impose any further -restrictions on the recipients' exercise of the rights granted herein. -You are not responsible for enforcing compliance by third parties to -this License. -
- If, as a consequence of a court judgment or allegation of patent -infringement or for any other reason (not limited to patent issues), -conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot -distribute so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you -may not distribute the Program at all. For example, if a patent -license would not permit royalty-free redistribution of the Program by -all those who receive copies directly or indirectly through you, then -the only way you could satisfy both it and this License would be to -refrain entirely from distribution of the Program. -
- If the distribution and/or use of the Program is restricted in -certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Program under this License may -add an explicit geographical distribution limitation excluding those -countries, so that distribution is permitted only in or among countries -not thus excluded. In such case, this License incorporates the -limitation as if written in the body of this License. -
- The Free Software Foundation may publish revised and/or new -versions of the General Public License from time to time. Such new -versions will be similar in spirit to the present version, but may -differ in detail to address new problems or concerns. -
- If you wish to incorporate parts of the Program into other free -programs whose distribution conditions are different, write to the -author to ask for permission. For software which is copyrighted by the -Free Software Foundation, write to the Free Software Foundation; we -sometimes make exceptions for this. Our decision will be guided by the -two goals of preserving the free status of all derivatives of our free -software and of promoting the sharing and reuse of software generally. +
- If the distribution and/or use of the Program is restricted in + certain countries either by patents or by copyrighted interfaces, the + original copyright holder who places the Program under this License may + add an explicit geographical distribution limitation excluding those + countries, so that distribution is permitted only in or among countries + not thus excluded. In such case, this License incorporates the + limitation as if written in the body of this License. +
- The Free Software Foundation may publish revised and/or new versions
+ of the General Public License from time to time. Such new versions will
+ be similar in spirit to the present version, but may differ in detail
+ to address new problems or concerns.
+
Each version is given a distinguishing version number. If the Program + specifies a version number of this License which applies to it and "any + later version", you have the option of following the terms and + conditions either of that version or of any later version published by + the Free Software Foundation. If the Program does not specify a version + number of this License, you may choose any version ever published by + the Free Software Foundation.
+
+ - If you wish to incorporate parts of the Program into other free + programs whose distribution conditions are different, write to the + author to ask for permission. For software which is copyrighted by the + Free Software Foundation, write to the Free Software Foundation; we + sometimes make exceptions for this. Our decision will be guided by the + two goals of preserving the free status of all derivatives of our free + software and of promoting the sharing and reuse of software generally.
- BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO -WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. - EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR -OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, -EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED -WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. - THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS -WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF -ALL NECESSARY SERVICING, REPAIR OR CORRECTION. -
- IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN -WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY -AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU -FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR -CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE -PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING -RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A -FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF -SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH -DAMAGES. +
- BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY + FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN + OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES + PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER + EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED + WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE + ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH + YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL + NECESSARY SERVICING, REPAIR OR CORRECTION. +
- IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN + WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY + AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU + FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR + CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE + PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING + RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A + FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF + SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH + DAMAGES.
- The modified work must itself be a software library. +
- The modified work must itself be a software library. -
- You must cause the files modified to carry prominent notices - stating that you changed the files and the date of any change. + +
- You must cause the files modified to carry prominent notices stating + that you changed the files and the date of any change. -
- You must cause the whole of the work to be licensed at no charge -to all third parties under the terms of this License. + +
- You must cause the whole of the work to be licensed at no charge to + all third parties under the terms of this License. -
- If a facility in the modified Library refers to a function or a - table of data to be supplied by an application program that uses the -facility, other than as an argument passed when the facility is -invoked, then you must make a good faith effort to ensure that, in the -event an application does not supply such function or table, the -facility still operates, and performs whatever part of its purpose -remains meaningful. -
- If a facility in the modified Library refers to a function or a
+ table of data to be supplied by an application program that uses the
+ facility, other than as an argument passed when the facility is
+ invoked, then you must make a good faith effort to ensure that, in the
+ event an application does not supply such function or table, the
+ facility still operates, and performs whatever part of its purpose
+ remains meaningful.
+
(For example, a function in a library to compute square roots has a + purpose that is entirely well-defined independent of the application. + Therefore, Subsection 2d requires that any application-supplied + function or table used by this function must be optional: if the + application does not supply it, the square root function must still + compute square roots.)
+ - Accompany the work with the complete corresponding - machine-readable source code for the Library including whatever - changes were used in the work (which must be distributed under - Sections 1 and 2 above); and, if the work is an executable linked - with the Library, with the complete machine-readable "work that uses -the Library", as object code and/or source code, so that the user can -modify the Library and then relink to produce a modified executable -containing the modified Library. (It is understood that the user who -changes the contents of definitions files in the Library will not -necessarily be able to recompile the application to use the modified -definitions.) +
- Accompany the work with the complete corresponding machine-readable + source code for the Library including whatever changes were used in the + work (which must be distributed under Sections 1 and 2 above); and, if + the work is an executable linked with the Library, with the complete + machine-readable "work that uses the Library", as object code and/or + source code, so that the user can modify the Library and then relink to + produce a modified executable containing the modified Library. (It is + understood that the user who changes the contents of definitions files + in the Library will not necessarily be able to recompile the + application to use the modified definitions.) -
- Accompany the work with a written offer, valid for at least three -years, to give the same user the materials specified in Subsection 6a, -above, for a charge no more than the cost of performing this -distribution. + +
- Accompany the work with a written offer, valid for at least three + years, to give the same user the materials specified in Subsection 6a, + above, for a charge no more than the cost of performing this + distribution. -
- If distribution of the work is made by offering access to copy - from a designated place, offer equivalent access to copy the above - specified materials from the same place. + +
- If distribution of the work is made by offering access to copy from + a designated place, offer equivalent access to copy the above specified + materials from the same place. -
- Verify that the user has already received a copy of these - materials or that you have already sent this user a copy. + +
- Verify that the user has already received a copy of these materials + or that you have already sent this user a copy.
- Accompany the combined library with a copy of the same work based -on the Library, uncombined with any other library facilities. This -must be distributed under the terms of the Sections above. +
- Accompany the combined library with a copy of the same work based on + the Library, uncombined with any other library facilities. This must be + distributed under the terms of the Sections above. -
- Give prominent notice with the combined library of the fact that -part of it is a work based on the Library, and explaining where to -find the accompanying uncombined form of the same work. + +
- Give prominent notice with the combined library of the fact that + part of it is a work based on the Library, and explaining where to find + the accompanying uncombined form of the same work.
- EPSON 9-pin Dot Matrix, epson9.ppd -
- EPSON 24-pin Dot Matrix, epson24.ppd +
- DYMO Label Printer, dymo.ppd +
- EPSON 9-pin Dot Matrix, epson9.ppd +
- EPSON 24-pin Dot Matrix, epson24.ppd -
- EPSON Stylus Color, stcolor.ppd -
- EPSON Stylus Photo, stphoto.ppd -
- HP DeskJet, deskjet.ppd -
- HP LaserJet, laserjet.ppd -
- EPSON Stylus Color, stcolor.ppd +
- EPSON Stylus Photo, stphoto.ppd +
- HP DeskJet, deskjet.ppd +
- HP LaserJet, laserjet.ppd + +
- WWW:
http://www.easysw.com-
+ - WWW:
+http://www.easysw.com/cups/ - EMail: info@easysw.com -
- Telephone (M-F, 9-5 EST): +1.301.373.9600 +
- Telephone (M-F, 9-5 EST): +1.301.373.9600
- not specifying the correct password for the root account. -
- accessing the CUPS server using the hostname or IP address of the -server without enabling remote access for administration functions. -This can be corrected by following the instructions in the -"I Can't Do Administration Tasks from Another Machine!" section -earlier in this appendix. -
- not setting a password on the root account. CUPS will not - authenticate a user account that does not have a password for - security reasons. -
- authenticating using an account other than root, but the account -you are using is not a member of the system group. -
- configuring CUPS to use Digest authentication, but your web -browser does not support Digest authentication. +
- not specifying the correct password for the root account. +
- accessing the CUPS server using the hostname or IP address of the + server without enabling remote access for administration functions. + This can be corrected by following the instructions in the +"I Can't Do Administration Tasks from Another Machine!" section + earlier in this appendix. +
- not setting a password on the root account. CUPS will not + authenticate a user account that does not have a password for security + reasons. +
- authenticating using an account other than root, but the account you + are using is not a member of the system group. +
- configuring CUPS to use Digest authentication, but your web browser + does not support Digest authentication.
|
@@ -1061,24 +1368,34 @@ determine how the server operates:
|
|
+ |
|
Description-The The The server name can be included in the filename by using The special name "syslog" can be used to send the access information -to the system log instead of a plain file. -The default access log file is /var/log/cups/access_log. + in the name. +The special name "syslog" can be used to send the access information + to the system log instead of a plain file. +The default access log file is /var/log/cups/access_log. Allow@@ -1163,14 +1487,16 @@ Allow from nnn.nnn.nnn.* Allow from nnn.nnn.nnn.nnn Allow from nnn.nnn.nnn.nnn/mm Allow from nnn.nnn.nnn.nnn/mmm.mmm.mmm.mmm +Allow from @LOCAL +Allow from @IF(name)Description-The The
The The AuthClass@@ -1202,22 +1531,21 @@ AuthClass GroupDescription-The
The
The AuthGroupName@@ -1231,10 +1559,10 @@ AuthGroupName lpDescriptionThe The AuthType@@ -1244,24 +1572,27 @@ Group authentication. AuthType None AuthType Basic AuthType Digest +AuthType BasicDigest Description-The
When using The
When using The AutoPurgeJobs@@ -1274,10 +1605,10 @@ AutoPurgeJobs NoDescription-The The BrowseAddress@@ -1288,27 +1619,30 @@ No. BrowseAddress 255.255.255.255:631 BrowseAddress 192.0.2.255:631 BrowseAddress host.domain.com:631 +BrowseAddress @LOCAL +BrowseAddress @IF(name)Description-The The default address is The The No browse addresses are set by default.
BrowseAllowExamples@@ -1320,18 +1654,23 @@ BrowseAllow from 192.0.2 BrowseAllow from 192.0.2.0/24 BrowseAllow from 192.0.2.0/255.255.255.0 BrowseAllow from *.domain.com +BrowseAllow from @LOCAL +BrowseAllow from @IF(name)Description-The The Host and domain name matching require that you enable the
- IP address matching supports exact matches, partial addresses that
-match networks using netmasks of 255.0.0.0, 255.255.0.0, and
-255.255.255.0, or network addresses using the specified netmask or bit
-count.
+ IP address matching supports exact matches, partial addresses that + match networks using netmasks of 255.0.0.0, 255.255.0.0, and + 255.255.255.0, or network addresses using the specified netmask or bit + count. +The BrowseDeny@@ -1345,60 +1684,65 @@ BrowseDeny from 192.0.2 BrowseDeny from 192.0.2.0/24 BrowseDeny from 192.0.2.0/255.255.255.0 BrowseDeny from *.domain.com +BrowseDeny from @LOCAL +BrowseDeny from @IF(name)Description-The The Host and domain name matching require that you enable the
- IP address matching supports exact matches, partial addresses that
-match networks using netmasks of 255.0.0.0, 255.255.0.0, and
-255.255.255.0, or network addresses using the specified netmask or bit
-count.
+ IP address matching supports exact matches, partial addresses that + match networks using netmasks of 255.0.0.0, 255.255.0.0, and + 255.255.255.0, or network addresses using the specified netmask or bit + count. +The BrowseOrder+BrowseIntervalExamples-BrowseOrder allow,deny -BrowseOrder deny,allow +BrowseInterval 0 +BrowseInterval 30 Description-The
The The BrowseInterval+ +BrowseOrderExamples-BrowseInterval 0 -BrowseInterval 30 +BrowseOrder allow,deny +BrowseOrder deny,allow Description-The The The
BrowsePollExamples@@ -1409,12 +1753,12 @@ BrowsePoll host.domain.com:631Description-The If The If BrowsePort@@ -1427,19 +1771,46 @@ BrowsePort 9999Description-The The
BrowseProtocols++ Examples+
+BrowseProtocols CUPS +BrowseProtocols SLP +BrowseProtocols CUPS SLP +BrowseProtocols all ++ + Description+The
BrowseRelayExamples@@ -1453,20 +1824,20 @@ BrowseRelay host.domain.com 192.0.2.255Description-The
The
BrowseRelay 127.0.0.1 255.255.255.255- This effectively provides access to printers on a WAN for all -clients on the LAN(s). + This effectively provides access to printers on a WAN for all clients + on the LAN(s). BrowseShortNames@@ -1479,12 +1850,12 @@ BrowseShortNames NoDescription-The The default value for this option is The The default value for this option is BrowseTimeout@@ -1497,14 +1868,14 @@ BrowseTimeout 60Description-The The The The Browsing@@ -1517,20 +1888,19 @@ Browsing OffDescription-The The
ClassificationExamples@@ -1545,11 +1915,45 @@ Classification unclassifiedDescription-The The ClassifyOverride++ Examples+
+ClassifyOverride Yes +ClassifyOverride No ++ + Description+The The default is to not allow classification overrides. + + +ConfigFilePerm++ Examples+
+ConfigFilePerm 0644 +ConfigFilePerm 0600 ++ + Description+The DataDir@@ -1561,8 +1965,8 @@ DataDir /usr/share/cupsDescription-The The DefaultCharset@@ -1576,10 +1980,10 @@ DefaultCharset windows-1251Description-The The DefaultLanguage@@ -1595,10 +1999,10 @@ DefaultLanguage itDescription-The The Deny@@ -1617,14 +2021,16 @@ Deny from nnn.nnn.nnn.* Deny from nnn.nnn.nnn.nnn Deny from nnn.nnn.nnn.nnn/mm Deny from nnn.nnn.nnn.nnn/mmm.mmm.mmm.mmm +Deny from @LOCAL +Deny from @IF(name)Description-The The
The The DocumentRoot@@ -1654,16 +2063,16 @@ DocumentRoot /foo/bar/doc/cupsDescription-The Documents are first looked up in a sub-directory for the primary
-language requested by the client (e.g. /usr/share/doc/cups/fr/...
-) and then directly under the The Documents are first looked up in a sub-directory for the primary
+ language requested by the client (e.g. /usr/share/doc/cups/fr/...
+) and then directly under the Encryption@@ -1674,14 +2083,13 @@ content by providing subdirectories for each language needed. Encryption Never Encryption IfRequested Encryption Required -Encryption AlwaysDescriptionThe ErrorLog@@ -1695,14 +2103,76 @@ ErrorLog syslogDescription-The The The server name can be included in the filename by using The special name "syslog" can be used to send the error information -to the system log instead of a plain file. + in the name. +The special name "syslog" can be used to send the error information + to the system log instead of a plain file. + + +FaxRetryInterval++ Examples+
+FaxRetryInterval 300 +FaxRetryInterval 30 ++ + Description+The The default setting is FaxRetryLimit++ Examples+
+FaxRetryLimit 5 +FaxRetryLimit 100 ++ + Description+The The default setting is FileDevice++ Examples+
+FileDevice Yes +FileDevice No ++ + Description+The The default setting is
FilterLimit@@ -1716,15 +2186,33 @@ FilterLimit 1000Description-The An average print to a non-PostScript printer needs a filter limit of -about 200. A PostScript printer needs about half that (100). Setting -the limit below these thresholds will effectively limit the scheduler -to printing a single job at any time. -The default limit is 0. + The An average print to a non-PostScript printer needs a filter limit of + about 200. A PostScript printer needs about half that (100). Setting + the limit below these thresholds will effectively limit the scheduler + to printing a single job at any time. +The default limit is 0. + + +FilterNice++ Examples+
+FilterNice 0 +FilterNice 39 +FilterNice -10 ++ + Description+The The default priority is 0. FontPath@@ -1737,9 +2225,9 @@ FontPath /usr/share/cups/fonts:/foo/bar/fontsDescription-The The Group@@ -1753,11 +2241,28 @@ Group rootDescription-The The HideImplicitMembers++ Examples+
+HideImplicitMembers Yes +HideImplicitMembers No ++ + Description+The
HostNameLookupsExamples@@ -1769,17 +2274,34 @@ HostNameLookups DoubleDescription-The The ImplicitAnyClasses++ Examples+
+ImplicitAnyClasses On +ImplicitAnyClasses Off ++ + Description+The
ImplicitClassesExamples@@ -1790,13 +2312,29 @@ ImplicitClasses OffDescription-The The Include++ Examples+
+Include filename +Include /foo/bar/filename ++ + Description+The KeepAliveExamples@@ -1807,12 +2345,12 @@ KeepAlive OffDescription-The HTTP/1.1 clients automatically support persistent connections, while
-HTTP/1.0 clients must specifically request them using the The HTTP/1.1 clients automatically support persistent connections, while
+ HTTP/1.0 clients must specifically request them using the KeepAliveTimeout@@ -1825,9 +2363,9 @@ KeepAliveTimeout 30Description-The The Limit@@ -1845,13 +2383,13 @@ default is 60 seconds.Description-The The LimitExcept@@ -1865,12 +2403,12 @@ type names are case-sensitive for compatibility with Apache.Description-The The LimitRequestBody@@ -1884,11 +2422,11 @@ LimitRequestBody 0Description-The The Also see the identical Listen@@ -1901,12 +2439,12 @@ Listen 192.0.2.1:631Description-The The The Location@@ -1922,16 +2460,76 @@ interfaces or networks. ... </Location> +<Location /printers> +... +</Location> + <Location /printers/name> ... </Location> + +<Location /classes> +... +</Location> + +<Location /classes/name> +... +</Location> + + +Description+The
Note that more specific resources override the less specific ones. So
+ the directives inside the LogFilePerm++ Examples+
+LogFilePerm 0644 +LogFilePerm 0600 Description-The The LogLevel@@ -1952,23 +2550,23 @@ LogLevel debug2Description-The
The
Description-The The
MaxJobs+MaxClientsPerHostExamples-MaxJobs 100 -MaxJobs 9999 -MaxJobs 0 +MaxClientsPerHost 0 +MaxClientsPerHost 10 Description-The Setting the maximum to 0 disables this functionality. The default -setting is 0. + The This directive provides a small measure of protection against Denial + of Service attacks from a single host. -MaxJobsPerPrinter+MaxCopies++ Examples+
+MaxCopies 100 +MaxCopies 65535 ++ + Description+The
MaxJobs++ Examples+
+MaxJobs 100 +MaxJobs 9999 +MaxJobs 0 ++ + Description+The Setting the maximum to 0 disables this functionality. The default + setting is 500. + + +MaxJobsPerPrinterExamples
Description-The Setting the maximum to 0 disables this functionality. The default -setting is 0. + The Setting the maximum to 0 disables this functionality. The default + setting is 0. MaxJobsPerUser@@ -2048,12 +2686,12 @@ MaxJobsPerUser 0Description-The Setting the maximum to 0 disables this functionality. The default -setting is 0. + The Setting the maximum to 0 disables this functionality. The default + setting is 0. MaxLogSize@@ -2067,11 +2705,11 @@ MaxLogSize 0Description-The Setting the maximum size to 0 disables log rotation. + The Setting the maximum size to 0 disables log rotation. MaxRequestSize@@ -2085,11 +2723,11 @@ MaxRequestSize 0Description-The The Also see the identical Order@@ -2102,16 +2740,16 @@ Order Deny,AllowDescription-The The
The PageLog@@ -2125,14 +2763,14 @@ PageLog syslogDescription-The The The server name can be included in the filename by using The special name "syslog" can be used to send the page information -to the system log instead of a plain file. + in the name. +The special name "syslog" can be used to send the page information to + the system log instead of a plain file. Port@@ -2145,48 +2783,49 @@ Port 80Description-The The PreserveJobHistory+PreserveJobFilesExamples-PreserveJobHistory On -PreserveJobHistory Off +PreserveJobFiles On +PreserveJobFiles Off Description-The A value of A value of The A value of A value of PreserveJobFiles+PreserveJobHistoryExamples-PreserveJobFiles On -PreserveJobFiles Off +PreserveJobHistory On +PreserveJobHistory Off Description-The A value of A value of The A value of A value of Printcap@@ -2200,18 +2839,18 @@ Printcap /etc/printers.confDescription-The When a filename is specified (e.g. /etc/printcap), the -printcap file is written whenever a printer is added or removed. The -printcap file can then be used by applications that are hardcoded to -look at the printcap file for the available printers. + The When a filename is specified (e.g. /etc/printcap), the + printcap file is written whenever a printer is added or removed. The + printcap file can then be used by applications that are hardcoded to + look at the printcap file for the available printers. -PrintcapFormat+PrintcapFormatExamples
Description-The The PrintcapGUI++ Example+
+PrintcapGUI /usr/bin/glpoptions ++ + Description+The The program must accept the ReloadTimeout++ Examples+
+ReloadTimeout 60 +ReloadTimeout 3600 +ReloadTimeout 0 ++ + Description+The RemoteRoot@@ -2235,10 +2910,10 @@ RemoteRoot rootDescription-The The RequestRoot@@ -2251,11 +2926,34 @@ RequestRoot /foo/bar/spool/cupsDescription-The The Require++ Examples+
+Require group foo bar +Require user john mary +Require valid-user ++ + Description+The The The The default is to do no authentication. This directive must appear
+ inside a RIPCache@@ -2269,11 +2967,28 @@ RIPCache 2048kDescription-The The RootCertDuration++ Examples+
+RootCertDuration 300 +RootCertDuration 0 ++ + Description+The RunAsUser@@ -2286,16 +3001,38 @@ RunAsUser NoDescription-The Note: Running as a non-priviledged user may prevent LPD and
-locally connected printers from working due to permission problems. The The Note: Running as a non-priviledged user may prevent LPD and
+ locally connected printers from working due to permission problems. The
+ Satisfy++ Examples+
+Satisfy all +Satisfy any ++ + Description+The Setting The default is ServerAdmin@@ -2308,10 +3045,10 @@ ServerAdmin root@foo.bar.comDescription-The The ServerBin@@ -2324,11 +3061,11 @@ ServerBin /foo/bar/lib/cupsDescription-The The ServerCertificate@@ -2340,12 +3077,12 @@ ServerCertificate /etc/cups/ssl/server.crtDescription-The The ServerKey@@ -2357,10 +3094,10 @@ ServerKey /etc/cups/ssl/server.keyDescription-The The ServerName@@ -2373,8 +3110,8 @@ ServerName myserver.domain.comDescription-The The ServerRoot@@ -2387,10 +3124,30 @@ ServerRoot /foo/bar/cupsDescription-The The ServerTokens++ Examples+
+ServerTokens None +ServerTokens ProductOnly +ServerTokens Major +ServerTokens Minor +ServerTokens Minimal +ServerTokens OS +ServerTokens Full ++ + Description+The SSLListen@@ -2403,12 +3160,12 @@ SSLListen 192.0.2.1:443Description-The The The SSLPort@@ -2420,9 +3177,9 @@ SSLPort 443Description-The The SystemGroup@@ -2436,10 +3193,10 @@ SystemGroup rootDescription-The The TempDir@@ -2452,13 +3209,13 @@ TempDir /foo/bar/tmpDescription-The Temporary directories must be world-writable and should have the -"sticky" permission bit enabled so that other users cannot delete -filter temporary files. The following commands will create an -appropriate temporary directory called /foo/bar/tmp: +The Temporary directories must be world-writable and should have the + "sticky" permission bit enabled so that other users cannot delete + filter temporary files. The following commands will create an + appropriate temporary directory called /foo/bar/tmp: mkdir /foo/bar/tmp ENTER @@ -2477,9 +3234,9 @@ Timeout 90 Description-The The User@@ -2492,22 +3249,720 @@ User guestDescription-The The Changing the Client Configuration+The CUPS client application ( Since the client configuration file consists of plain text, you can + use your favorite text editor to make changes to it. + + +Client Directives+The client.conf file contains two directives that + determine how the client behaves: +
Encryption++ Examples+
+Encryption Never +Encryption IfRequested +Encryption Required +Encryption Always ++ + Description+The ServerName++ Examples+
+ServerName foo.bar.com +ServerName 11.22.33.44 ++ + Description+The Changing the Printer Configuration+The CUPS scheduler (cupsd) uses the /etc/cups/printers.conf + file to store the list of available printers. This file contains only + locally defined printers, but not remote printers that are created + automatically. Each directive is listed on a line by itself followed by + its value. Comments are introduced using the number sign ("#") + character at the beginning of a line. +Since the printer configuration file consists of plain text, you can + use your favorite text editor to make changes to it. + + +Printer Directives+The printers.conf file contains many directives that + determine how the printer behaves: +
Accepting++ Examples+
+Accepting yes + +Accepting no ++ + Description+The This directive must appear inside a AllowUser++ Examples+
+AllowUser foo_user +AllowUser bar_user ++ + Description+The This directive must appear inside a DefaultPrinter++ Examples+
+<DefaultPrinter name/> +... +</Printer> ++ + Description+The DenyUser++ Examples+
+DenyUser foo_user +DenyUser bar_user ++ + Description+The This directive must appear inside a DeviceURI++ Examples+
+DeviceURI socket://foo.bar.com:9100 ++ + Description+The This directive must appear inside a Info++ Examples+
+Info My Printer ++ + Description+The This directive must appear inside a JobSheets++ Examples+
+JobSheets none,standard ++ + Description+The The
If only one banner file is specified, it will be printed before the + files in the job. If a second banner file is specified, it is printed + after the files in the job. +The available banner pages depend on the local system configuration; + CUPS includes the following banner files: +
This directive must appear inside a KLimit++ Examples+
+KLimit 1234 ++ + Description+The This directive must appear inside a Location++ Examples+
+Location Building 3321 ++ + Description+The
This directive must appear inside a PageLimit++ Examples+
+PageLimit 1234 ++ + Description+The This directive must appear inside a Printer++ Examples+
+<Printer name/> +... +</Printer> ++ + Description+The QuotaPeriod++ Examples+
+QuotaPeriod 604800 ++ + Description+The This directive must appear inside a State++ Examples+
+State stopped ++ + Description+The This directive must appear inside a StateMessage++ Examples+
+StateMessage Ready to print. ++ + Description+The
This directive must appear inside a Changing the Classes Configuration+The CUPS scheduler (cupsd) uses the /etc/cups/classes.conf + file to store the list of available classes. This file contains only + locally defined classes, but not remote or implicit classes that are + created automatically. Each directive is listed on a line by itself + followed by its value. Comments are introduced using the number sign + ("#") character at the beginning of a line. +Since the classes configuration file consists of plain text, you can + use your favorite text editor to make changes to it. + + +Classes Directives+The classes.conf file contains many directives that + determine how the classes behaves: +
Accepting++ Examples+
+Accepting yes + +Accepting no ++ + Description+The This directive must appear inside a AllowUser++ Examples+
+AllowUser foo_user +AllowUser bar_user ++ + Description+The This directive must appear inside a Class++ Examples+
+<Class name/> +... +</Class> ++ + Description+The DefaultClass++ Examples+
+<DefaultClass name/> +... +</DefaultClass> ++ + Description+The DenyUser++ Examples+
+DenyUser foo_user +DenyUser bar_user ++ + Description+The This directive must appear inside a Info++ Examples+
+Info My Printer ++ + Description+The This directive must appear inside a JobSheets++ Examples+
+JobSheets none,standard ++ + Description+The The
If only one banner file is specified, it will be printed before the + files in the job. If a second banner file is specified, it is printed + after the files in the job. +The available banner pages depend on the local system configuration; + CUPS includes the following banner files: +
This directive must appear inside a KLimit++ Examples+
+KLimit 1234 ++ + Description+The This directive must appear inside a Location++ Examples+
+Location Building 3321 ++ + Description+The
This directive must appear inside a PageLimit++ Examples+
+PageLimit 1234 ++ + Description+The This directive must appear inside a Printer++ Examples+
+Printer foo +Printer bar +Printer foo@bar ++ + Description+The
This directive must appear inside a QuotaPeriod++ Examples+
+QuotaPeriod 604800 ++ + Description+The This directive must appear inside a State++ Examples+
+State stopped ++ + Description+The This directive must appear inside a StateMessage++ Examples+
+StateMessage Ready to print. ++ + Description+The
This directive must appear inside a Printing System Security-CUPS provides support for address, certificate, and password (Basic -and Digest) based authentication and access control. Certificate and -password authentication provide ways to limit access to individual -people or groups. -Address based access control allows you to limit access to specific -systems, networks, or domains. While this does not provide -authentication, it does allow you to limit the potential users of your -system efficiently. -CUPS maintains a list of locations that have access control and/or
-authentication enabled. Locations are specified using the
- CUPS provides support for address, certificate, and password (Basic + and Digest) based authentication and access control. Certificate and + password authentication provide ways to limit access to individual + people or groups. +Address based access control allows you to limit access to specific + systems, networks, or domains. While this does not provide + authentication, it does allow you to limit the potential users of your + system efficiently. +CUPS maintains a list of locations that have access control and/or
+ authentication enabled. Locations are specified using the
+ <Location /resource> @@ -2522,8 +3977,8 @@ authentication enabled. Locations are specified using the Locations generally follow the directory structure of the
-
The CUPS implementation of Basic authentication does not allow -access through user accounts without a password. If you try to -authenticate using an account without a password, your access will be -immediately blocked. -Once a valid username and password is authenticated by CUPS, any -additional group membership requirements are checked. + The CUPS implementation of Basic authentication does not allow access + through user accounts without a password. If you try to authenticate + using an account without a password, your access will be immediately + blocked. +Once a valid username and password is authenticated by CUPS, any + additional group membership requirements are checked.
Use the Use the AuthType Basic @@ -2612,43 +4064,41 @@ AuthType Basic - lppasswd -a user ENTER @@ -2658,7 +4108,7 @@ Password again: (password) ENTER [password is not echoed] - lppasswd ENTER @@ -2669,40 +4119,39 @@ Password again: (password) ENTER [password is not echoed] - lppasswd -x user ENTER- Once a valid username and password is authenticated by CUPS, any -additional group membership requirements are checked. + Once a valid username and password is authenticated by CUPS, any + additional group membership requirements are checked.
Use the Use the AuthType Digest- System and Group Authentication-The System and Group Authentication+The For root group; the actual group depends on
+ the operating system.
+For <Location /path> @@ -2712,10 +4161,10 @@ AuthGroupName mygroup </Location>- The named group must be a valid UNIX user group, usually defined in -the /etc/group or /etc/netgroup files. -Additionally, when using Digest authentication you need to create user -accounts with the named group: +The named group must be a valid UNIX user group, usually defined in + the /etc/group or /etc/netgroup files. + Additionally, when using Digest authentication you need to create user + accounts with the named group: lppasswd -g mygroup -a user ENTER @@ -2726,15 +4175,15 @@ Password again: (password) ENTER [password is not echoed] host group user date-time \"method resource version\" status bytes @@ -2743,37 +4192,38 @@ host group user date-time \"method resource version\" status bytes 127.0.0.1 - mike [20/May/1999:19:20:31 +0000] "POST /admin/ HTTP/1.1" 200 0- The host field will normally only be an IP address unless you
-have enabled the The group field always contains "-" in CUPS. -The user field is the authenticated username of the -requesting user. If no username and password is supplied for the -request then this field contains "-". -The date-time field is the date and time of the request in -local time and is in the format: +The host field will normally only be an IP address unless you
+ have enabled the The group field always contains "-" in CUPS. +The user field is the authenticated username of the requesting + user. If no username and password is supplied for the request then this + field contains "-". +The date-time field is the date and time of the request in + local time and is in the format: [DD/MON/YYYY:HH:MM:SS +ZZZZ]- where ZZZZ is the timezone offset in hours and minutes from -Greenwich Mean Time (a.k.a. GMT a.k.a. ZULU.) -The method field is the HTTP method used ("GET", "PUT", -"POST", etc.) -The resource field is the filename of the requested resource. -The version field is the HTTP specification version used by -the client. For CUPS clients this will always be "HTTP/1.1". -The status field contains the HTTP result status of the -request. Usually it is "200", but other HTTP status codes are possible. -For example, 401 is the "unauthorized access" status in the example -above. -The bytes field contains the number of bytes in the request. -For POST requests the bytes field contains the number of bytes -that was received from the client. -The error_log File-The error_log file lists messages from the scheduler -(errors, warnings, etc.): +where ZZZZ is the timezone offset in hours and minutes from + coordinated universal time (UTC). UTC may sometimes be referred to as + GMT or ZULU on legacy systems. +The method field is the HTTP method used ("GET", "PUT", + "POST", etc.) +The resource field is the filename of the requested resource. +The version field is the HTTP specification version used by + the client. For CUPS clients this will always be "HTTP/1.1". +The status field contains the HTTP result status of the + request. Usually it is "200", but other HTTP status codes are possible. + For example, 401 is the "unauthorized access" status in the example + above. +The bytes field contains the number of bytes in the request. + For POST requests the bytes field contains the number of bytes + that was received from the client. +The error_log File+The error_log file lists messages from the scheduler + (errors, warnings, etc.): level date-time message @@ -2783,110 +4233,115 @@ I [20/May/1999:19:21:02 +0000] Job 2 queued on 'DeskJet' by 'mike'. I [20/May/1999:19:22:24 +0000] Job 2 was cancelled by 'mike'.- The level field contains the type of message: +The level field contains the type of message:
The date-time field contains the date and time of when the -page started printing. The format of this field is identical to the -data-time field in the access_log file. -The message fields contains a free-form textual message. -The page_log File-The page_log file lists each page that is sent to a -printer. Each line contains the following information: +The date-time field contains the date and time of when the + page started printing. The format of this field is identical to the + data-time field in the access_log file. +The message fields contains a free-form textual message. +The page_log File+The page_log file lists each page that is sent to a + printer. Each line contains the following information: -printer user job-id date-time page-number num-copies job-billing +printer user job-id date-time page-number num-copies job-billing hostname -DeskJet root 2 [20/May/1999:19:21:05 +0000] 1 0 acme-123 -- - The printer field contains the name of the printer that -printed the page. If you send a job to a printer class, this field will -contain the name of the printer that was assigned the job. -The user field contains the name of the user (the IPP The job-id field contains the job number of the page being -printed. Job numbers are reset to 1 whenever the CUPS server is -started, so don't depend on this number being unique! -The date-time field contains the date and time of when the -page started printing. The format of this field is identical to the -data-time field in the access_log file. -The page-number and num-pages fields contain the page -number and number of copies being printed of that page. For printer -that can not produce copies on their own, the num-pages field -will always be 1. -The job-billing field contains a copy of the The printer field contains the name of the printer that + printed the page. If you send a job to a printer class, this field will + contain the name of the printer that was assigned the job. +The user field contains the name of the user (the IPP The job-id field contains the job number of the page being + printed. Job numbers are reset to 1 whenever the CUPS server is + started, so don't depend on this number being unique! +The date-time field contains the date and time of when the + page started printing. The format of this field is identical to the + data-time field in the access_log file. +The page-number and num-pages fields contain the page + number and number of copies being printed of that page. For printer + that can not produce copies on their own, the num-pages field + will always be 1. +The job-billing field contains a copy of the The hostname field contains the name of the host (the IPP File Typing and Filtering-CUPS provides a MIME-based file typing and filtering mechanism to -convert files to a printable format for each printer. On startup the -CUPS server reads MIME database files from the /etc/cups + CUPS provides a MIME-based file typing and filtering mechanism to
+ convert files to a printable format for each printer. On startup the
+ CUPS server reads MIME database files from the /etc/cups
directory (or a directory specified by the The mime.types and mime.convs files define the -standard file types and filters that are available on the system. -mime.types-The mime.types file defines the known file types. Each
-line of the file starts with the MIME type and may be followed by one
-or more file type recognition rules. For example, the The mime.types and mime.convs files define the + standard file types and filters that are available on the system. +mime.types+The mime.types file defines the known file types. Each
+ line of the file starts with the MIME type and may be followed by one
+ or more file type recognition rules. For example, the text/html html htm \ - printable(0,1024) + \ - (string(0,"<HTML>") string(0,"<!DOCTYPE")) -- - The first two rules say that any file with an extension of .html
- or .htm is a HTML file. The third rule says that any file
-whose first 1024 characters are printable text and starts with the
-strings The first two rules deal solely with the name of the file being -typed. This is useful when the original filename is known, however for -print files the server doesn't have a filename to work with. The third -rule takes care of this possibility and automatically figures out the -file type based upon the contents of the file instead. -The available tests are: -
All numeric values can be in decimal (123), octal (0123), or -hexadecimal (0x123) as desired. + printable(0,1024) + \ + (string(0,"<HTML>") string(0,"<!DOCTYPE")) + + + The first two rules say that any file with an extension of .html
+ or .htm is a HTML file. The third rule says that any file
+ whose first 1024 characters are printable text and starts with the
+ strings The first two rules deal solely with the name of the file being + typed. This is useful when the original filename is known, however for + print files the server doesn't have a filename to work with. The third + rule takes care of this possibility and automatically figures out the + file type based upon the contents of the file instead. +The available tests are: +
All numeric values can be in decimal (123), octal (0123), or + hexadecimal (0x123) as desired. -Strings can be in quotes, all by themselves, as a string of -hexadecimal values, or some combination: +Strings can be in quotes, all by themselves, as a string of + hexadecimal values, or some combination: "string" @@ -2896,26 +4351,27 @@ string <7374>ring- As shown in the As shown in the image/jpeg jpeg jpg jpe string(0,<FFD8FF>) &&\ - (char(3,0xe0) char(3,0xe1) char(3,0xe2) char(3,0xe3)\ - char(3,0xe4) char(3,0xe5) char(3,0xe6) char(3,0xe7)\ - char(3,0xe8) char(3,0xe9) char(3,0xea) char(3,0xeb)\ - char(3,0xec) char(3,0xed) char(3,0xee) char(3,0xef)) + (char(3,0xe0) char(3,0xe1) char(3,0xe2) char(3,0xe3)\ + char(3,0xe4) char(3,0xe5) char(3,0xe6) char(3,0xe7)\ + char(3,0xe8) char(3,0xe9) char(3,0xea) char(3,0xeb)\ + char(3,0xec) char(3,0xed) char(3,0xee) char(3,0xef))- This rule states that any file with an extension of .jpeg
-, .jpg, or .jpe is a JPEG file. In addition, any
-file starting with the hexadecimal string mime.convs-The mime.convs file defines all of the filter programs -that are known to the system. Each line consists of: +This rule states that any file with an extension of .jpeg,
+ .jpg, or .jpe is a JPEG file. In addition, any file
+ starting with the hexadecimal string mime.convs+The mime.convs file defines all of the filter programs + that are known to the system. Each line consists of: source destination cost program @@ -2926,107 +4382,109 @@ image/* application/vnd.cups-postscript 50 imagetops image/* application/vnd.cups-raster 50 imagetoraster- The source field is a MIME type, optionally using a wildcard -for the super-type or sub-type (e.g. "text/plain", "image/*", -"*/postscript"). -The destination field is a MIME type defined in the -mime.types file. -The cost field defines a relative cost for the filtering
-operation from 1 to 100. The cost is used to choose between two
-different sets of filters when converting a file. For example, to
-convert from The source field is a MIME type, optionally using a wildcard
+ for the super-type or sub-type (e.g. "text/plain", "image/*",
+ "*/postscript"). The destination field is a MIME type defined in the
+ mime.types file. The cost field defines a relative cost for the filtering
+ operation from 1 to 100. The cost is used to choose between two
+ different sets of filters when converting a file. For example, to
+ convert from The program field defines the filter program to run; the
-special program "-" can be used to make two file types equivalent. The
-program must accept the standard filter arguments and environment
-variables described in the CUPS Interface Design Description and CUPS
-Software Programmers Manual: The program field defines the filter program to run; the + special program "-" can be used to make two file types equivalent. The + program must accept the standard filter arguments and environment + variables described in the CUPS Interface Design Description and CUPS + Software Programmers Manual: program job user title options [filename]- If specified, the filename argument defines a file to read -when filtering, otherwise the filter must read from the standard input. -All filtered output must go to the standard output. + If specified, the filename argument defines a file to read + when filtering, otherwise the filter must read from the standard input. + All filtered output must go to the standard output. -Adding Filetypes and Filters-Adding a new file type or filter is fairly straight-forward. Rather -than adding the new type and filter to the mime.types and -mime.convs files which are overwritten when you upgrade to a new -version of CUPS, you simple need to create new files with .types - and .convs extensions in the /etc/cups - directory. We recommend that you use the product or format name, e.g.: +Adding Filetypes and Filters+Adding a new file type or filter is fairly straight-forward. Rather + than adding the new type and filter to the mime.types and + mime.convs files which are overwritten when you upgrade to a new + version of CUPS, you simple need to create new files with .types + and .convs extensions in the /etc/cups directory. + We recommend that you use the product or format name, e.g.: myproduct.types myproduct.convs- If you are providing a filter for a common file format or printer, -add the company or author name: +If you are providing a filter for a common file format or printer, + add the company or author name: acme-msword.types -acme.msword.convs +acme-msword.convs- This will help to prevent name collisions if you install many -different file types and filters. -Once you choose the names for these files, create them using your
-favorite text editor as described earlier in this chapter. Once you
-have created the files, restart the Printer Drivers and PPD Files-Most CUPS printer drivers utilize one or more printer-specific
-filters and a PPD file for each printer model. Printer driver filters
-are registered via the PPD file using This will help to prevent name collisions if you install many + different file types and filters. +Once you choose the names for these files, create them using your
+ favorite text editor as described earlier in this chapter. Once you
+ have created the files, restart the Printer Drivers and PPD Files+Most CUPS printer drivers utilize one or more printer-specific
+ filters and a PPD file for each printer model. Printer driver filters
+ are registered via the PPD file using *cupsFilter: "application/vnd.cups-raster 0 rastertohp"- The filter is specified using the source file type only; the
-destination file type is assumed to be Writing Your Own Filter or Printer Driver-CUPS supports an unlimited number of file formats and filters, and -can handle any printer. If you'd like to write a filter or printer -driver for your favorite file format or printer, consult the CUPS -Software Programmers Manual for step-by-step instructions. -7 - Printing with Other -Systems-This chapter describes how to print from client systems that use the -LPD, Mac OS, or Windows printing protocols. +The filter is specified using the source file type only; the
+ destination file type is assumed to be Writing Your Own Filter or Printer Driver+CUPS supports an unlimited number of file formats and filters, and + can handle any printer. If you'd like to write a filter or printer + driver for your favorite file format or printer, consult the CUPS + Software Programmers Manual for step-by-step instructions. +7 - Printing with Other + Systems+This chapter describes how to print from client systems that use the + LPD, Mac OS, or Windows printing protocols. The Basics-CUPS is based on the IPP protocol, so any system that supports IPP -can send jobs to and receive jobs from CUPS automatically. However, not -all systems support IPP yet. This chapter will show you how to connect -these systems to your CUPS server, either to accept jobs from your -server for printing, or to send jobs to your server. +CUPS is based on the IPP protocol, so any system that supports IPP + can send jobs to and receive jobs from CUPS automatically. However, not + all systems support IPP yet. This chapter will show you how to connect + these systems to your CUPS server, either to accept jobs from your + server for printing, or to send jobs to your server. Printing from LPD Clients-CUPS supports limited functionality for LPD-based clients. With LPD -you can print files to specific printers, list the queue status, and so -forth. However, the automatic client configuration and printer options -are not supported by the LPD protocol, so you must manually configure -each client for the printers it needs to access. -The CUPS supports limited functionality for LPD-based clients. With LPD + you can print files to specific printers, list the queue status, and so + forth. However, the automatic client configuration and printer options + are not supported by the LPD protocol, so you must manually configure + each client for the printers it needs to access. +The printer stream tcp nowait lp /usr/lib/cups/daemon/cups-lpd cups-lpd- The path to the Once you have added this line, send the The path to the Once you have added this line, send the killall -HUP inetd ENTER [IRIX and some versions of Linux] @@ -3034,40 +4492,97 @@ installation. reboot ENTER [For all systems if the HUP signal fails]- Printing to LPD Servers-CUPS provides the Microsoft Windows NT provides an LPD service under the name "TCP/IP -Printing Services". To enable LPD printing on NT, open the "Services" -control panel, select the "TCP/IP Printing Services" service, and click -on the "Start" button. Any shared printer will then be available via -the LPD protocol. -Printing from Mac OS Clients-CUPS does not provide Mac OS support directly. However, there are -several free and commercial software packages that do. -Columbia Appletalk Package (CAP)-Because the CAP LaserWriter server ( If you are using the
+service printer
+{
+socket_type = stream
+protocol = tcp
+wait = no
+user = lp
+server = /usr/lib/cups/daemon/cups-lpd
+}
+
+
+The
Printing to LPD Servers+CUPS provides the Microsoft Windows NT provides an LPD service under the name "TCP/IP + Printing Services". To enable LPD printing on NT, open the "Services" + control panel, select the "TCP/IP Printing Services" service, and click + on the "Start" button. Any shared printer will then be available via + the LPD protocol. + + +Printing from Mac OS 10.2 and Later Clients+Since Mac OS 10.2 uses CUPS as its printing system, all CUPS printers + will be available to the clients automatically. +
Printing from Mac OS 10.1 and Earlier Clients+CUPS does not provide support for Mac OS 10.1 and earlier directly. + However, there are several free and commercial software packages that + do. +Columbia Appletalk Package (CAP)+Because the CAP LaserWriter server ( lwsrv -n "Name" -p printer -a /usr/lib/adicts -f /usr/lib/LW+Fonts- where where XINET KA/Spool-To use your system as a print server for Mac OS clients, configure
-each printer using a XINET KA/Spool+To use your system as a print server for Mac OS clients, configure
+ each printer using a /usr/etc/appletalk/papserver -I -L -P /etc/cups/ppd/MyPrinter.ppd \ @@ -3077,36 +4592,47 @@ PPD file in the /etc/cups/ppd directory for each printer. -Printer Description:MyPrinter@MyServer:\ - :pr=|/usr/bin/lp -d MyPrinter:\ - :op=daemon:\ - :pd=/etc/cups/ppd/MyPrinter.ppd: +Printer Name@Zone Name:\ +:pr=|/usr/bin/lp -d MyPrinter:\ +:op=daemon:\ +:pd=/etc/cups/ppd/MyPrinter.ppd:- Printing to Mac OS Servers-CUPS currently does not provide a backend to communicate with a Mac
-OS server. However, you can write and install a short shell script in
-the /usr/lib/cups/backend directory that sends a print file
-using the appropriate command. The following is a short script that
-will run the After copying this script to /usr/lib/cups/backend/cap,
-specify a device URI of Printing to Mac OS 10.2 and Later Servers+Since MacOS 10.2 and later use CUPS, all you need to do is enable + printer sharing to allow CUPS clients to print to a Mac OS server. You + will need to download and install ESP Ghostscript on your server to + provide PostScript printing support for non-PostScript printers, + however. + + +Printing to Mac OS 10.1 and Earlier Servers+CUPS currently does not provide a backend to communicate with a Mac
+ OS 10.1 and earlier server. However, you can write and install a short
+ shell script in the /usr/lib/cups/backend directory that
+ sends a print file using the appropriate command. The following is a
+ short script that will run the After copying this script to /usr/lib/cups/backend/cap,
+ specify a device URI of
Printing from Windows Clients-While CUPS does not provide Windows support directly, the free SAMBA -software package does. SAMBA version 2.0.6 is the first release of -SAMBA that supports CUPS. You can download SAMBA from: +Printing from Windows Clients+While CUPS does not provide Windows support directly, the free SAMBA + software package does. SAMBA version 2.0.6 is the first release of + SAMBA that supports CUPS. You can download SAMBA from: http://www.samba.org- To configure SAMBA for CUPS, edit the smb.conf file and -replace the existing printing commands and options with the line: +To configure SAMBA for CUPS, edit the smb.conf file and + replace the existing printing commands and options with the line: printing = cups +printcap name = cups ++ + That's all there is to it! Remote users will now be able to browse + and print to printers on your system. +Exporting Printer Drivers+You can optionally export printer drivers from your CUPS server using
+ the Before you can export the printers you must download the CUPS drivers
+ for Windows from the CUPS site (
+http://www.cups.org/) or the current Adobe PostScript printer
+ drivers from the Adobe web site (
+http://www.adobe.com/). If you download the Adobe drivers, use the
+ free
+ADFONTS.MFM +ADOBEPS4.DRV +ADOBEPS4.HLP +ADOBEPS5.DLL +ADOBEPSU.DLL +ADOBEPSU.HLP +DEFPRTR2.PPD +ICONLIB.DLL +PSMON.DLL ++ + Copy these files to the /usr/share/cups/drivers directory + - you may need to rename some of the files so the filenames are all + UPPERCASE. +Next, configure SAMBA (via the smb.conf file) to support + printing through CUPS and provide a printer driver download share, as + follows: +
+[global] +load printers = yes +printing = cups +printcap name = cups + +[printers] +comment = All Printers +path = /var/spool/samba +browseable = no +public = yes +guest ok = yes +writable = no +printable = yes +printer admin = root + +[print$] +comment = Printer Drivers +path = /etc/samba/drivers +browseable = yes +guest ok = no +read only = yes +write list = root ++ + This configuration assumes a FHS-compliant installation of SAMBA;
+ adjust the [printers] and [print$] share paths accordingly on your
+ system as needed. That is, the directory for your printer drivers can
+ be anywhere on the system; just make sure it is writable by the users
+ specified by the Finally, run the
+cupsaddsmb -U root printer1 ... printerN ENTER ++ + Running
+cupsaddsmb -U root -a ENTER- That's all there is to it! Remote users will now be able to browse -and print to printers on your system. -Printing to Windows Servers-CUPS can print to Windows servers in one of two ways. The first way -uses the LPD protocol on the CUPS system and the "TCP/IP Printing -Services" on the Windows system. You can find out more about this -configuration in the LPD section earlier in this -chapter. -The second way is through the Microsoft Server Message Block ("SMB") -protocol. Support for this protocol is provided with the free SAMBA -software package. You can download SAMBA from: +Notice in the above examples that the user Printing to Windows Servers+CUPS can print to Windows servers in one of two ways. The first way + uses the LPD protocol on the CUPS system and the "TCP/IP Printing + Services" on the Windows system. You can find out more about this + configuration in the LPD section earlier in this + chapter. +The second way is through the Microsoft Server Message Block ("SMB") + protocol. Support for this protocol is provided with the free SAMBA + software package. You can download SAMBA from: http://www.samba.org- To configure CUPS for SAMBA, run the following command: +To configure CUPS for SAMBA, run the following command: ln -s `which smbspool` /usr/lib/cups/backend/smb ENTER- The The smb://workgroup/server/sharename @@ -3217,96 +4827,125 @@ smb://user:pass@workgroup/server/sharename smb://user:pass@server/sharename- The The A - Software License Agreement-Common UNIX Printing System License -Agreement-Copyright 1997-2001 by Easy Software Products + Common UNIX Printing System License + Agreement+Copyright 1997-2005 by Easy Software Products
Introduction-The Common UNIX Printing SystemTM, ("CUPSTM"), -is provided under the GNU General Public License ("GPL") and GNU -Library General Public License ("LGPL"), Version 2. A copy of these -licenses follow this introduction. -The GNU LGPL applies to the CUPS API library, located in the "cups" -subdirectory of the CUPS source distribution and in the -"/usr/include/cups" directory and "libcups.a", "libcups.sl", or -"libcups.so" files in the binary distributions. -The GNU GPL applies to the remainder of the CUPS distribution, -including the "pstoraster" filter which is based upon GNU Ghostscript -5.50 and the "pdftops" filter which is based upon Xpdf 0.90. -For those not familiar with the GNU GPL, the license basically -allows you to: -
What this license does not allow you to do is make changes or -add features to CUPS and then sell a binary distribution without source -code. You must provide source for any new drivers, changes, or -additions to the software, and all code must be provided under the GPL -or LGPL as appropriate. -The GNU LGPL relaxes the "link-to" restriction, allowing you to -develop applications that use the CUPS API library under other licenses -and/or conditions as appropriate for your application. -Trademarks-Easy Software Products has trademarked the Common UNIX Printing -System, CUPS, and CUPS logo. These names and logos may be used freely -in any direct port or binary distribution of CUPS. To use them in -derivative products, please contract Easy Software Products for written -permission. Our intention is to protect the value of these trademarks -and ensure that any derivative product meets the same high-quality -standards as the original. -Binary Distribution Rights-Easy Software Products also sells rights to the CUPS source code -under a binary distribution license for vendors that are unable to -release source code for their drivers, additions, and modifications to -CUPS under the GNU GPL and LGPL. For information please contact us at -the address shown above. -The Common UNIX Printing System provides a "pstoraster" filter that -utilizes the GNU GhostScript 5.50 core to convert PostScript files into -a stream of raster images. For binary distribution licensing of this -software, please contact: Miles Jones -- - The "pdftops" filter is based on the Xpdf 0.90 software. For binary -distribution licensing of this software, please contact: - Derek B. Noonburg + |