cups-lpd(8) Apple Inc. cups-lpd(8)NAMEcups-lpd - receive print jobs and report printer status to lpd clients
SYNOPSIScups-lpd [ -h hostname[:port] ] [ -n ] [ -o option=value ]
DESCRIPTIONcups-lpd is the CUPS Line Printer Daemon ("LPD") mini-server that sup‐
ports legacy client systems that use the LPD protocol. cups-lpd does
not act as a standalone network daemon but instead operates as a
socket-activatable systemd(1) service.
Sets the CUPS server (and port) to use.
Disables reverse address lookups; normally cups-lpd will try to
discover the hostname of the client via a reverse DNS lookup.
Inserts options for all print queues. Most often this is used to
disable the "l" filter so that remote print jobs are filtered as
needed for printing; the examples in the previous section set the
"document-format" option to "application/octet-stream" which
forces autodetection of the print file format.
PERFORMANCEcups-lpd performs well with small numbers of clients and printers. How‐
ever, since a new process is created for each connection and since each
process must query the printing system before each job submission, it
does not scale to larger configurations. We highly recommend that large
configurations use the native IPP support provided by CUPS instead.
SECURITYcups-lpd currently does not perform any access control based on the
settings in cupsd.conf(5) or in the hosts.allow(5) or hosts.deny(5)
files used by TCP wrappers. Therefore, running cups-lpd on your server
will allow any computer on your network (and perhaps the entire Inter‐
net) to print to your server.
You should use configure the firewall to limit TCP port 515 access to
only those computers that should be able to print through your server.
cups-lpd is not enabled by the standard CUPS distribution. Please con‐
sult with your operating system vendor to determine whether it is
enabled on your system.
COMPATIBILITYcups-lpd does not enforce the restricted source port number specified
in RFC 1179, as using restricted ports does not prevent users from sub‐
mitting print jobs. While this behavior is different than standard
Berkeley LPD implementations, it should not affect normal client opera‐
The output of the status requests follows RFC 2569, Mapping between LPD
and IPP Protocols. Since many LPD implementations stray from this defi‐
nition, remote status reporting to LPD clients may be unreliable.
SEE ALSOcups(1), cupsd(8), systemd(1), http://localhost:631/help
Copyright 2007-2013 by Apple Inc.
4 August 2008 CUPS cups-lpd(8)