EVOLUTION-MANAGER
Edit File: man-cups-lpd.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <!-- SECTION: Man Pages --> <head> <link rel="stylesheet" type="text/css" href="../cups-printable.css"> <title>cups-lpd(8)</title> </head> <body> <h1 class="title">cups-lpd(8)</h1> <h2 class="title"><a name="NAME">Name</a></h2> cups-lpd - receive print jobs and report printer status to lpd clients <h2 class="title"><a name="SYNOPSIS">Synopsis</a></h2> <b>cups-lpd </b>[ -h <i>hostname[:port] </i>] [ -n ] [ -o <i>option=value </i>] <h2 class="title"><a name="DESCRIPTION">Description</a></h2> <i>cups-lpd</i> is the CUPS Line Printer Daemon ("LPD") mini-server that supports legacy client systems that use the LPD protocol. <i>cups-lpd</i> does not act as a standalone network daemon but instead operates as a socket-activatable <i>systemd(1)</i> service. <h2 class="title"><a name="OPTIONS">Options</a></h2> <dl> <dt>-h hostname[:port] </dt> <dd></dd> <dd>Sets the CUPS server (and port) to use. </dd> <dt>-n </dt> <dd></dd> <dd>Disables reverse address lookups; normally <i>cups-lpd</i> will try to discover the hostname of the client via a reverse DNS lookup. </dd> <dt>-o name=value </dt> <dd></dd> <dd>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. </dd> </dl> <h2 class="title"><a name="PERFORMANCE">Performance</a></h2> <i>cups-lpd</i> performs well with small numbers of clients and printers. However, 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. <h2 class="title"><a name="SECURITY">Security</a></h2> <i>cups-lpd</i> currently does not perform any access control based on the settings in <a href='man-cupsd.conf.html?TOPIC=Man+Pages'>cupsd.conf(5)</a> or in the <i>hosts.allow(5)</i> or <i>hosts.deny(5)</i> files used by TCP wrappers. Therefore, running <i>cups-lpd</i> on your server will allow any computer on your network (and perhaps the entire Internet) to print to your server. <p>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. <p><i>cups-lpd</i> is not enabled by the standard CUPS distribution. Please consult with your operating system vendor to determine whether it is enabled on your system. <h2 class="title"><a name="COMPATIBILITY">Compatibility</a></h2> <i>cups-lpd</i> does not enforce the restricted source port number specified in RFC 1179, as using restricted ports does not prevent users from submitting print jobs. While this behavior is different than standard Berkeley LPD implementations, it should not affect normal client operations. <p>The output of the status requests follows RFC 2569, Mapping between LPD and IPP Protocols. Since many LPD implementations stray from this definition, remote status reporting to LPD clients may be unreliable. <h2 class="title"><a name="EXAMPLE">Example</a></h2> CUPS includes configuration files for Simply enable the <b>cups-lpd </b>socket using the corresponding control program. <pre> systemctl enable cups-lpd.socket systemctl start cups-lpd.socket </pre> <h2 class="title"><a name="SEE_ALSO">See Also</a></h2> <i>cups(1)</i>, <a href='man-cupsd.html?TOPIC=Man+Pages'>cupsd(8)</a>, <i>systemd(1)</i>, <a href='http://localhost:631/help'>http://localhost:631/help</a> <h2 class="title"><a name="COPYRIGHT">Copyright</a></h2> Copyright 2007-2013 by Apple Inc. </body> </html>