CUPS is a more recent printing system that was initially designed to support the Internet Printing Protocol (IPP) but has evolved into a drop-in replacement for both the BSD and System V utilities, including client replacements for RFC 1179 (lpd protocol) support.
Although it retains backward compatibility with older printing systems, the internal details of CUPS are significantly different. The server component cupsd handles queuing, and includes a web server for configuration and management. Nearly everything can be configured through the web interface or the included lpadmin command. The various configuration files in the /etc/cups directory rarely need to be edited by hand.
The CUPS web interface, shown in Figure 18-1, is available on the machine at http://localhost:631.
In order to implement or troubleshoot a printing system, it’s very important to understand the data flow and the steps taken on the server and client side. In the case of CUPS, these are:
A print job is generated by an application locally on the client side.
The print job is sent to the print server specified by the protocol selected for that queue (e.g., IPP or CIFS).
On the CUPS server, the spooler process cupsd fetches the data stream and saves it in the print spool directory. The default directory is /var/spool/cups.
If an input filter is specified in the configuration, ...