The device-uri refers to a serial device with configurable baud rate and other options.
+If the device-uri contains a baud value, it represents the maximum baud rate supported by the device.
The
scheme
-field provides the URI scheme that is supported by the backend. Backends should use this form only when the backend supports any URI using that scheme. The
+field provides the URI scheme that is supported by the backend.
+Backends should use this form only when the backend supports any URI using that scheme.
+The
device-uri
field specifies the full URI to use when communicating with the device.
The
device-make-and-model
-field specifies the make and model of the device, e.g. "Example Foojet 2000". If the make and model is not known, you must report "Unknown".
+field specifies the make and model of the device, e.g. "Example Foojet 2000".
+If the make and model is not known, you must report "Unknown".
The
device-info
-field specifies additional information about the device. Typically this includes the make and model along with the port number or network address, e.g. "Example Foojet 2000 USB #1".
+field specifies additional information about the device.
+Typically this includes the make and model along with the port number or network address, e.g. "Example Foojet 2000 USB #1".
The optional
device-id
field specifies the IEEE-1284 device ID string for the device, which is used to select a matching driver.
@@ -109,7 +116,8 @@ field specifies the IEEE-1284 device ID string for the device, which is used to
device-location
field specifies the physical location of the device, which is often used to pre-populate the printer-location attribute when adding a printer.
-Backends without world read and execute permissions are run as the root user. Otherwise, the backend is run using an unprivileged user account, typically "lp".
+Backends without world read and execute permissions are run as the root user.
+Otherwise, the backend is run using an unprivileged user account, typically "lp".
The following exit codes are defined for backends:
@@ -117,28 +125,35 @@ The following exit codes are defined for backends:
- The print file was successfully transmitted to the device or remote server.
- CUPS_BACKEND_FAILED
-The print file was not successfully transmitted to the device or remote server. The scheduler will respond to this by canceling the job, retrying the job, or stopping the queue depending on the state of the
+The print file was not successfully transmitted to the device or remote server.
+The scheduler will respond to this by canceling the job, retrying the job, or stopping the queue depending on the state of the
printer-error-policy
attribute.
- CUPS_BACKEND_AUTH_REQUIRED
-
- The print file was not successfully transmitted because valid authentication information is required. The scheduler will respond to this by holding the job and adding the 'cups-held-for-authentication' keyword to the "job-reasons" Job Description attribute.
+
- The print file was not successfully transmitted because valid authentication information is required.
+The scheduler will respond to this by holding the job and adding the 'cups-held-for-authentication' keyword to the "job-reasons" Job Description attribute.
- CUPS_BACKEND_HOLD
-
- The print file was not successfully transmitted because it cannot be printed at this time. The scheduler will respond to this by holding the job.
+
- The print file was not successfully transmitted because it cannot be printed at this time.
+The scheduler will respond to this by holding the job.
- CUPS_BACKEND_STOP
-
- The print file was not successfully transmitted because it cannot be printed at this time. The scheduler will respond to this by stopping the queue.
+
- The print file was not successfully transmitted because it cannot be printed at this time.
+The scheduler will respond to this by stopping the queue.
- CUPS_BACKEND_CANCEL
-
- The print file was not successfully transmitted because one or more attributes are not supported or the job was canceled at the printer. The scheduler will respond to this by canceling the job.
+
- The print file was not successfully transmitted because one or more attributes are not supported or the job was canceled at the printer.
+The scheduler will respond to this by canceling the job.
- CUPS_BACKEND_RETRY
-
- The print file was not successfully transmitted because of a temporary issue. The scheduler will retry the job at a future time - other jobs may print before this one.
+
- The print file was not successfully transmitted because of a temporary issue.
+The scheduler will retry the job at a future time - other jobs may print before this one.
- CUPS_BACKEND_RETRY_CURRENT
-
- The print file was not successfully transmitted because of a temporary issue. The scheduler will retry the job immediately without allowing intervening jobs.
+
- The print file was not successfully transmitted because of a temporary issue.
+The scheduler will retry the job immediately without allowing intervening jobs.
All other exit code values are reserved.
In addition to the environment variables listed in
-cups(1)
+cups(1)
and
-filter(7),
+filter(7),
CUPS backends can expect the following environment variable:
- DEVICE_URI
@@ -147,20 +162,28 @@ CUPS backends can expect the following environment variable:
/etc/cups/cups-files.conf
-CUPS backends are not generally designed to be run directly by the user. Aside from the device URI issue (
+CUPS backends are not generally designed to be run directly by the user.
+Aside from the device URI issue (
argv[0]
and
DEVICE_URI
-environment variable contain the device URI), CUPS backends also expect specific environment variables and file descriptors, and typically run in a user session that (on macOS) has additional restrictions that affect how it runs. Backends can also be installed with restricted permissions (0500 or 0700) that tell the scheduler to run them as the "root" user instead of an unprivileged user (typically "lp") on the system.
-
Unless you are a developer and know what you are doing, please do not run backends directly. Instead, use the
-lp(1)
+environment variable contain the device URI), CUPS backends also expect specific environment variables and file descriptors, and typically run in a user session that (on macOS) has additional restrictions that affect how it runs.
+Backends can also be installed with restricted permissions (0500 or 0700) that tell the scheduler to run them as the "root" user instead of an unprivileged user (typically "lp") on the system.
+
Unless you are a developer and know what you are doing, please do not run backends directly.
+Instead, use the
+lp(1)
or
-lpr(1)
+lpr(1)
programs to send print jobs or
-lpinfo(8)
-to query for available printers using the backend. The one exception is the SNMP backend - see
-cups-snmp(8)
+lpinfo(8)
+to query for available printers using the backend.
+The one exception is the SNMP backend - see
+cups-snmp(8)
for more information.
+
+CUPS printer drivers and backends are deprecated and will no longer be supported in a future feature release of CUPS.
+Printers that do not support IPP can be supported using applications such as
+ippeveprinter(1).
cups(1),
cups-files.conf(5),
@@ -173,7 +196,7 @@ for more information.
CUPS Online Help (http://localhost:631/help)
-Copyright © 2007-2018 by Apple Inc.
+Copyright © 2007-2019 by Apple Inc.