Translation(s): none

Setting up and administering print queues within the CUPS printing system.

A document destined for a printer is frequently called a print job. On its way to the printer it is first put into a queue before being processed. The queue has certain properties which determine how the print job is dealt with and may be queried with lpoptions and lpstat for a list of some of these properties and the queue status repectively.

The properties specified when the queue is created are not immutable. Quite a few of them can be altered by a user when the print job is submitted to the queue. An administrator who hoped to confine users to duplex (two-sided) printing with two pages per sheet of paper would have to look outside the CUPS framework for a solution to add to the system.

Several queues can point to the same physical device, the printer, but it is very common for "print queue" and "printer" to be used interchangably. Generally no harm comes from this.

The device-uri

Ultimately, a print job has to go somewhere. Most users expect the "somewhere" to be a printer. To see which "somewhere"s you have open to you, do (as root or a user):

  /usr/sbin/lpinfo -v

The backends in /usr/lib/cups/backends are now used in discovery mode in an endeavour to locate printers. Here is the output of one such command when two printers are attached to the machine via a USB and parallel port and one is available over the network:

  network ipps
  network http
  network lpd
  network ipp14
  network socket
  network https
  direct parallel:/dev/lp0
  network ipp
  serial serial:/dev/ttyS0?baud=115200
  serial serial:/dev/ttyS1?baud=115200
  direct usb://EPSON/Stylus%20COLOR%20740
  network dnssd://TEST1%20%40%20wheezy._ipp._tcp.local/cups
  network dnssd://TEST2%20%40%20wheezy._ipp._tcp.local/cups
  network dnssd://TEST3%20%40%20wheezy._ipp._tcp.local/cups
  network socket://

The USB-connected printer and the networked one have definitely been discovered. They have device-uris


A parallel port has also been found. Its device-uri is


To identify the makes and models of any printers you will want to do

  lpinfo -l -v

In this case, an edited output is

  Device: uri = usb://EPSON/Stylus%20Photo%20RX420?serial=LJ4O40407152301540&interface=1
          class = direct
          info = EPSON Stylus Photo RX420
          make-and-model = EPSON Stylus Photo RX420
          device-id = MFG:EPSON;CMD:ESCPL2,BDC,D4;MDL:Stylus Photo RX420;CLS:PRINTER;DES:EPSON Stylus Photo RX420;
          location =
  Device: uri = parallel:/dev/lp0
          class = direct
          info = EPSON Stylus COLOR 740 LPT #1
          make-and-model = EPSON Stylus COLOR 740
          device-id = MFG:EPSON;CMD:ESCPL2,BDC,D4;MDL:Stylus COLOR 740;CLS:PRINTER;
          location =
  Device: uri = socket://
          class = network
          info = HP LaserJet 2200
          make-and-model = HP LaserJet 2200
          device-id = G:Hewlett-Packard;CMD:PJL,MLC,PCL,PCLXL,POSTSCRIPT;MDL:HP LaserJet 2200;CLS:PRINTER;DES:Hewlett-Packard LaserJet 2200;MEM:8MB
          location =

The dnssd://... entries are either Bonjour-broadcasted print queues on a remote machine or Bonjour-enabled printers; DNS-SD has located them with the help of Avahi. In general, queues created with a dnssd://... device-uri should be set up as raw queues so that the filtering takes place entirely on the remote machine. If it is known that the queue on the remote machine is itself a raw one you may have to consider whether setting up a local queue achieves what you want, (see Tea4CUPS for situations in which you would want a local raw queue). A Bonjour-enabled printer would almost certainly require a local non-raw queue to be set up for it.

Which dnssd://... entries are queues and which are printers?

/usr/lib/cups/backend/dnssd > dnssd.log

grep "local/cups" dnssd.log      (These are print queues).
grep "local/?uuid" dnssd.log     (These are printers).
grep "Unknown" dnssd.log         (These are raw print queues).

A client machine with a cups version greater than or equal to 1.6.x will have the same dnssd://... queues found with avahi-daemon plus cups-browsed and listed with

   lpstat -t

The device-uri for a Networked Printer

CUPS can use at least one of the AppSocket, Internet Printing (IPP) and Line Printer (LPD) protocols for connecting to printers and print servers over a network connection. For a view of which services a device supports there is thenmap command:

nmap <ip_address_or_hostname>

The output will vary from printer to printer. For an HP Envy 4500 it is

80/tcp   open  http
443/tcp  open  https
631/tcp  open  ipp
8080/tcp open  http-proxy
9100/tcp open  jetdirect
9220/tcp open  unknown

The choice of protocol will be driven by your needs and what is offered by the printer or print server. AppSocket is non-complex, usually well-implemented, low overhead and reliably gets the data from point A to point B, but doesn't do much else. IPP provides bidirectional communication for feedback and control, secure authentication services, access control and printer discovery and status. Its use is mandatory on AirPrint and IPP Everywhere printers. LPD is a popular protocol older than IPP and with a feature set less extensive than it. Secure access, detailed error status reports and the ability to query a printer are lacking, for example.

Also known as the JetDirect or RAW protocol it is the most basic protocol that can be supported by a printer. The URI scheme is


The standard port number is 9100 and this will be used by default if omitted from the device-uri. Print servers with three outputs would require three port numbers; for example, 9100, 9101 and 9102.

It is questionable whether AppSocket is a protocol. There is no specified standard for it; no queue management; no aborting of jobs; no querying of printer supplies; no encryption. All it does is shovel the data for a print-ready file over the network and then close the connection. Because the only overhead is TCP/IP the data transfer is generally fast. Also, it has been in widespread use for a long time so the printer implementations of AppSocket are good.

Printing normally takes place over port 631 with the URI scheme being


Unfortunately, the resource path has never been standardised and it may require some experimentation to determine what a printer or server will accept, especially if the device is not on the local network. Apparently, newer printers use /ipp/print in the path but for older products it could be something entirely different, like ipp/port1 or ipp. Maybe the printer's front panel will help. Or

/usr/lib/cups/backend/snmp <ip_address>

could give suitable output if there is explicit information from the Port Monitor MIB (Management Information Base) database of the printer. In the absence of an MIB the probing is for AppSocket then LPD and the first that works is reported. Because AppSocket is supported by most network printers it would likely be the "protocol" given for use in a URI.

If an IPP printer has registered itself using Avahi (DNS-SD/mDNS) more success with obtaining an IPP URI could be achieved by installing cups-ipp-utils and running ippfind:

ippfind                         (Shows IPP printers and print queues).
ippfind -T 5                    (Possibly more reliable).
ippfind ! --txt printer-type    (Show IPP printers only).

A CUPS server can always be reached with


In theory, the handshaking and status monitoring done by the IPP protocol should ensure reliable printing but, in practice, there are older printers which do not implement some aspects of IPP very well. However, these days, a more optimistic view of the situation can be taken.

This is the original network protocol. It has a URI scheme of


and a default port of 515. Even though AppSocket and IPP are seen as better alternatives it is regarded as a reliable protocol for sending a job to a printer. CUPS itself has some limited functionality for LPD-based clients

Configuring the Choice of Backend

The cups package provides a debconf method for selecting backends which are used for printer discovery and connection to the device. It basically gives a convenient way of copying the backends which come with CUPS between /usr/lib/cups/backend-available/ and /usr/lib/cups/backend/. Run

dpkg-reconfigure cups

Note that not every backend on the system is managed with this command because they are not all in the cups package. For example, the parallel backend is in the cups-filters package.

Be careful about which backends are removed from the debconf list. Deleting the dnssd backend would still allow remote Bonjour broadcasted queue discovery via cups-browsed but Bonjour broadcasted printers would not seen. An AppSocket-enabled printer would be discoverable with the snmp backend but, if the socket backend was deleted, trying to set up a queue using a socket://... URI would give the error Bad device-uri scheme "socket".

Printer Drivers

The job of a printer driver is to ensure that printing options are applied by the scheduler and the filtering system and produce a final output which can be understood by the printer.

Drivers are in the printer-driver-* packages plus various other packages. The print server task in Debian Installer gives you a full complement of these drivers. You may decline this task at install time but after first boot can do either

  apt-get install task-print-server


  apt-get install cups

If a driver/PPD for your printer is not in any of the installed packages you have various choices open to you:

   apt-cache search search_term

Non-free Printer Drivers and Firmware

Some driver software distributed with some printers does not meet the criterion of being DFSG-free, so users will have to rely on what the printer manufacturer has to offer to get their printer working. Also, even though their drivers are DFSG-free, some printers require proprietary firmware to allow full access to printer features and enhanced performance. The firmware is uploaded to the printer when it is powered-on attached to the computer.

It may also be necessary to go to the manufacturer's website if the printer is a new model and drivers for it are not yet in a Debian package.

Solutions for Linux is a good place to start for assessing what support your printer has from Brother. Generally, you will need .deb files for the cupswrapper and the lpr driver. Follow the instructions to install them; alternatively, there is linux-brprinter-installer to do that for you.

There is a wiki page dealing with Canon URF-II printers which should suffice for installing all Canon's package offerings.

Linux support for a Samsung printer can be searched for from the Printers link at the Samsung Download Center. Many, but not all, Samsung printer models use the Unified Linux Driver (ULD). ULD contains PPDs for Linux supported printers, a printer driver to use with the PPDs and a library to use with the driver. It comes in a .tar.gz package and only supports the i386 and amd64 platforms. No source code is provided.

Extract the files in the tarball and install them by entering the directory created and running

tar zvxf uld_v1.00.xx_xx.xx.tar.gz
cd uld

Samsung does not provide ULD as a .deb but the The Samsung Unified Linux Driver Repository does. It also has a good deal of information on the installation of ULD and its interaction with a Debian system. SULDR is not affiliated with Samsung.

Some HP devices require a plugin to be installed on the computer for them to operate at all or to function at their full potential for one or more of the device's printing, scanning or faxing modes. For a small number of HP printers the plugin contains firmware which has to be uploaded to a printer. Without a firmware requirement the plugin software is still needed to interact with the printer. Effectively, the print job is processed by the plugin to produce a file in a language the printer understands. In technical literature the printer would be described as host-based. See whether the plugin is needed and use HP's home page search facility to see a printer's details and find out what any firmware is required for.

Any needed firmware can be installed when hplip is installed and the command hp-plugin -i is issued to get the plugin (firmware) file for the particular HPLIP release. HPLIP can probably be removed after this is done if the hp backend is not preferred for printing or if hp-setup is not needed to establish a print queue.

Not the name of a printer manufacturer but a Debian package which can install firmware and colour profiles for a number of printers which use the ZjStream wire protocol. The commands (as root)

getweb | less
getweb p1008

give a list of what is available and download the firmware file for an HP LaserJet P1008. Hannah is a graphical firmware downloader which uses getweb. Re-plug the connection to the printer to upload the firmware to it.

Avoiding Non-free Printer Drivers and Firmware

A non-free filter generally gets used at the last stage of the filtering process after cups-filters has done its job. The process ends with something that is sometimes termed host-based (and which is often proprietary) rather than letting the printer itself take care of the final conversion. It makes sense to the printer manufacturer to do this (probably on legal, technical or economic grounds) but it disrupts the free software ecosystem within which CUPS and cups-filters operate.

           +----------------------+    +-----------------+
File in -> |CUPS and cups-filters | -> | Non-free driver | -> Printer
           +----------------------+    +-----------------+

The final stage of this process could be dispensed with if what was sent to the printer was something it could understand.

           +-----------------------+    | Something the printer  |
File in -> | CUPS and cups-filters | -> | understands sent by    | -> Printer
           +-----------------------+    | CUPS and cups filters. |        

Recent developments in printer technology see printers understanding MIME types image/pwg-raster and image/urf. These file types are also referred to as PWG and Apple raster data formats respectively.

           +-----------------------+    | Apple raster |
File in -> | CUPS and cups-filters | -> | or           | -> Printer
           +-----------------------+    | PWG raster   |     

From CUPS 2.2.2 and cups-filters 1.13.0 onwards it is possible to send a job in Apple and PWG raster to a printer which understands either data format. This is dealt with in more detail on the driverless printing page.

The PPD file

PostScript Printer Description (PPD) files were originally used by printers which operated with PostScript as a Page Description Language (PDL) for printing. They have been adapted to cope with other standard printer languages such as HP's Printer Command Language (PCL) and special (often proprietary) languages. Driver packages include PPDs in their contents.

A searchable list of PPDs on your system is obtained with

  lpinfo -m | less

If there is only one for your printer the choice is made for you! If there is more than one, go for the PPD which is marked "Recommended". If none are recommended use common sense (sometimes called "guessing" :) ) or seek help from the openprinting database.

Some Generic PPDs are listed with lpinfo -m and one may be a solution when every driver package is installed and your printer model is not in the list. You can also resort to the printer manufacturer's website or a CD which came with the printer.

It is convenient (and probably sensible) to put a PPD obtained from elsewhere in /usr/share/ppd/custom. It will then be displayed in the output of lpinfo -m and by the web interface.

Creating a Print Queue with lpadmin

This is the basic method to set up a queue. It is used behind the scenes with programs like system-config-printer, HPLIP and the web interface. There are four essentials to provide when setting up a working, accepting print queue with lpadmin.

  1. The queue name (-p): The printing system treats the name in a case-insensitive manner; LaserJet-300 is the same queue as laserjet-300.

  2. The device-uri (-v): The destination for a print job; usually a printer.

  3. The PPD file (-m or -P): Determines how the print job is handled by the filtering system to produce data which can be successfully printed by the printer.

  4. Whether the queue is enabled (-E}: Must be specified explicitly.

With this information:

  lpadmin -p queue_name -v device-uri -m PPD_file -E

sets up the queue.

Sometimes it is necessary or desirable to establish a raw queue. That is, a queue where the filtering system is not involved and the print job goes directly to a printer or another queue.

  lpadmin -p queue_name -v device-uri -m raw

lpoptions is the command to use to see default printer-specific options (obtained from the PPD) for the queue.

  lpoptions -p queue_name -l

Options which are not specific to the particular printer come from

  lpoptions -p queue_name

The previous lpadmin command is about as simple as it gets for setting up a queue quickly but it can be tweaked just as simply by giving the command some printer-specific and non-specific options to add with -o.

The lpadmin and lp manuals are sources for non-PPD options.

Setting up a queue requires either root privileges or for the user to be a member of the lpadmin group. If you installed CUPS using the print server task in the Debian installer the first user is put in the lpadmin group.

Check for user membership of the lpadmin group with the command


Creating a Print Queue with the CUPS Web Interface

http://localhost:631 is the location of the interface and from there you can administer print queues, including their installation. Administration tasks are able to be completed by giving the root name and password or the user name and password of an lpadmin group member.

The Add Printer button could produce a first page with something like this on it:

             Local Printers:    Serial Port #1
                                Serial Port #2
                                EPSON Stylus Photo RX420 (EPSON Stylus Photo RX420)
                                EPSON Stylus COLOR 740 LPT #1 (EPSON Stylus COLOR 740)
Discovered Network Printers:    TEST1 @ wheezy (HP HP DesignJet 750C)
                                TEST2 @ wheezy (HP HP DesignJet 750C)
                                TEST3 @ wheezy
                                HP LaserJet 2200 (HP LaserJet 2200)
     Other Network Printers:    AppSocket/HP JetDirect
                                Internet Printing Protocol (ipps)
                                Internet Printing Protocol (ipp14)
                                Internet Printing Protocol (https)
                                Internet Printing Protocol (http)
                                LPD/LPR Host or Printer
                                Internet Printing Protocol (ipp)

Which doesn't look significantly different from what lpinfo -l -v gave previously.

Under Local Printers: are the discovered printers which are directly connected to the machine being used. Discovered Network Printers: are networked printers on the same subnet as your machine. Or they could be print queues which the dnssd backend has found on the same subnet. In both cases backends have been run in discovery mode to find printers. The device-uri found is on the second page.

Other Network Printers: gives you the opportunity to provide the device uri and ppd for a printer or queue which falls into neither of the previous two categories. The information is provided on the second and third pages.

Having made a selection from Local Printers: or Discovered Network Printers: you should find a queue name based on the printer make and model has been filled in for you on the next page. Change it by all means if you wish. Once it is done it cannot be modified later because a new name would imply setting up a different, new queue.

Share printers connected to this system on the Administration page is the basic facility to allow (or not allow) DNS-SD broadcasting on Debian 8.x.x. Ticking Share This Printer on the second page designates your queue as one to add to this facility.

Moving on to the third page you should find that a PPD has been selected for you, unless

The previous driver and ppd comments apply here too.

The final page has the printer-specific options from the PPD and a few non-specific printer options. This should suit the needs of many users.

Creating a Print Queue with HPLIP

HPLIP is a one-stop solution for printing, scanning and faxing with appropriate HP devices and designed to work with CUPS. Only the printing aspect is dealt with here. HPLIP uses its own printer backend, hp, and URI scheme for printer discovery and sending a print-ready job to the printer. For a graphical user interface (GUI) to HPLIP there is a package which contains very similar utilities to the ones in HPLIP.


hp:/net/<printer_model>?zc=<zeroconf(avahi, Bonjour)_hostname>

hp:/par/<printer_model>?device=/dev/parportX (X=1,2...)

Printer discovery and setting up a print queue can be done from the command line with hp-setup. For USB and printers on the network:

hp-setup -i -busb
hp-setup -i -bnet

You will be led through the rest of the procedure.

hp-setup uses one of two methods to find printers on the network - Service Location Protocol (SLP) and mdns (Bonjour) broadcasts from suitable printers.

The SLP service agent runs on port 427 of a printer; do you have one?

  • nmap -sU -p 427 <ip_address>

will tell you.

The command hp-setup -i -bnet only uses SLP for discovery. If you want to setup a queue for an mdns advertised printer it is suggested to do

  1. hp-probe -mmdns (This provides a Device URI).
  2. hp-setup -i -d<Device URI>

A problem with firewall settings could lead to the first command failing.

Some HP printers require non-free firmware to operate at their full potential.

Creating a Print Queue with system-config-printer

The idea of system-config-printer is to provide functionality similar to lpadmin and the CUPS web interface but with GTK+ widgets and greater desktop integration. Anyone familiar with the CUPS web interface should feel at home with it but note that there is a difference in the way adminstrator privileges for the printing system are gained.

A default system-config-printer installs cups-pk-helper as a recommended package to further the aim of desktop integration. cups-pk-helper is intended to give fine-grained control of aspects of CUPS management via policykit. Unlike lpadmin, the CUPS web interface and HPLIP cups-pk-helper does not respect the SystemGroup lpadmin directive in /etc/cups/cups-files.conf and an adminstrator password will be requested to see remote print queues and to administer them and local queues.


Almost nothing is administratively possible for an ordinary user when cups-pk-helper is on the machine. A user is entitled to cancel her own jobs but without the machine's administrator altering policykit's view of who is entitled to administer printers nothing else is available.

This can be done with a file ending with .pkla put into /etc/polkit-1/localauthority/50-local.d. With the contents

[Printer configuration]

the users milly, molly, mandy would have privileges granted similar to those granted to a member of the lpadmin group and not have to provide a password. Removing the cups-pk-helper package would be an alternative strategy to allow users in the lpadmin group administrative privileges.

The initial screen seen when system-config-printer is run displays icons and names for local print queues; that is, queues which been set up by a user or by cups-browsed. The Add button is for printer discovery and creating a new queue for a printer. A greyed-out button indicates a lack of some administrative privilege so go to Server-->Connect-->Connect. Hopefully, the device-uri section will be found useful for interpreting the discovered printers display.

Double Filtering

The CUPS web interface and the command /usr/sbin/lpinfo -v give a list of printers and print queues discovered on the network. Any of the entries in the list can be installed as a local print queue. In other words they will listed in /etc/cups/printers.conf on your machine.

For example, under Discovered Network Printers in the web interface you might see

  testq@desktop (DCP-9020CDW)

and the next web page shows a Connection beginning dnssd://.

The dnssd:// tells you this is a print queue discoverd by avahi-daemon. The (DCP-9020CDW) tells you the make and model of the printer. This latter information is obtained from the *Product line in the queue's PPD, so it implies the queue is not a raw queue and a job sent to it undergoes filtering. The same information is given in the make-and-model field of the output of /usr/sbin/lpinfo -l -v.

On the third web page you should choose Raw as the Make. With lpadmin you should have no -m option or -m raw. Then the client passes the data through without filtering and all filtering is done correctly on the server.

Alternatively, you can get such queues automatically set up locally by running cups-browsed on the client.

Upstream CUPS has something to say about double filtering. Quoting:

The issue is the MIME typing on the CUPS server - if the server
doesn't recognize the MIME media type then you may end up with
extra filtering.

I'm not saying it can't work (because we have customers that use
that configuration all of the time), it is just that we get a lot
of support calls when people try to do Microsoft-style printer
sharing to a server that is also hosting a CUPS printer driver on
the same queue.

Reinforcing the previous point:

The issue is that for IPP we actually get to use MIME media types,
and the filters in the PPD file specify what the final output type
is. We then try to match things up on the remote system, which is
where the problems typically occur. For example, if the local
driver has a filter that specifies application/vnd.hp-pcl" as the
destination MIME media type but the server does not have that MIME
media type defined/supported for its queue, we have to revert to
"application/octet-stream" (auto-detect).

You can "fix" this with .types and .convs files on the server 
to specify a "-" filter for the affected MIME media types to
application/vnd.cups-raw) but ultimately you are better off
letting the server do the filtering...

You are strongly advised not to do double filtering. Set up the queue on the client as a raw queue if the remote queue is doing the filtering.


This package was introduced for CUPS 1.6.x and is necessary on a Debian 8.x client machine if you want to discover print queues broadcast with DNS-SD (Bonjour broadcasting) and have them available in the print dialogues of GUI applications and usable by command line programs. Documention is in /usr/share/doc/cups/README.Debian.gz, /etc/cups/cups-browsed.conf, cups-browsed and cups-browsed.conf. The avahi-daemon package also needs to be installed on the client. The default cups-browsed.conf is set to do both DND-SD (Bonjour) and CUPS discovery of print queues.

A server with a CUPS version of 1.6.x or greater does not need cups-browsed to do DNS-SD broadcasting but avahi-daemon is required.

DNS-SD Broadcasting (Server)

DNS-SD Discovery (Client)

Debian Version





cups-browsed needed

Not available


Not available
Use dnssd backend


avahi-daemon needed





CUPS Broadcasting (Server)

CUPS Discovery (Client)

Debian Version





cups-browsed needed

Not available


Not available


avahi-daemon needed





Printing and GTK Applications

The section on cups-browsed might give the impression that no printing can take place from a Debian 8.x.x client without it. This is not quite the case; it all depends on what you are printing from. Nevertheless it is worth repeating that cups-browsed promotes printing from all applications and from the command line.

Iceweasel, Evince and gedit (to name three) use the GTK print dialog as a printing subsystem. The subsystem gets print queue information directly from Avahi and the queues appear in the print dialogues of applications. cups-browsed isn't needed and neither for that matter is CUPS.

The print dialogues of Qt applications (Okular, Konqueror etc) and LibreOffice do not have this feature as yet.

Printing Without a Local CUPS Server

Print queue availability using browsing is a dynamic process. Queues will come and go as they are enabled and disabled or as a machine is moved from network to network. In a world which more and more has a focus on mobile devices there are benefits to be gained from avahi-daemon and cups-browsed or from a print dialogue which implements Avahi discovery itself.

However, it is possible a static configuration is entirely suitable for some purposes. In other words, no avahi-daemon, no cups-browsed and no cupsd running on a machine and instead connecting to a designated server. The first step is to read this manual. Then

  apt-get install cups-client

followed by making the directory ~/.cups and putting a file client.conf in it.

  mkdir ~/.cups
  touch ~/.cups/client.conf

The content of client.conf could be as simple as


The local queue is eliminated and print jobs from all applications and the command line go straight to ServerName for processing. There is the bother of changing ServerName when moving from network to network but this may be balanced by not having to run three daemons,

Even a client.conf may be dispensed with if the only printing to take place is from the command line. At its simplest:

  lp -h server_IP_or_hostname -d print_queue_on_server print_job

Configuration Files for the Scheduler, cupsd

These are located in /etc/cups as cupsd.conf and cups-files.conf. The existence of two files arises from a Debian bug report which lead to the fixing of a privilege escalation from lpadmin to root on systems with all options contained in cupsd.conf. as they were at that time.

cups-files is editable only by root. cupsd.conf can be edited by root and, from the web interface only, by a user who is a member of the lpadmin group. After editing either file cupsd has to be restarted:

  service cups restart

It can be very convenient to change some of the cupsd.conf settings with cupsctl (as root only). The current settings displayed by


might be


Change a displayed setting with

  cupsctl Webinterface=no

and, for a setting which is not displayed:

  cupsctl SystemdIdleExit=Off

More than one line in cupsd.conf can be changed with some commands and cupsd is restarted when cupsctl is used. cups-files cannot be altered with cupsctl.

See Also