]> git.ipfire.org Git - thirdparty/cups.git/blob - doc/help/man-cups-lpd.html
Save work.
[thirdparty/cups.git] / doc / help / man-cups-lpd.html
1 <!DOCTYPE HTML>
2 <html>
3 <!-- SECTION: Man Pages -->
4 <head>
5 <link rel="stylesheet" type="text/css" href="../cups-printable.css">
6 <title>cups-lpd(8)</title>
7 </head>
8 <body>
9 <h1 class="title">cups-lpd(8)</h1>
10 <h2 class="title"><a name="NAME">Name</a></h2>
11 cups-lpd - receive print jobs and report printer status to lpd clients
12 <h2 class="title"><a name="SYNOPSIS">Synopsis</a></h2>
13 <b>cups-lpd</b>
14 [ -h
15 <i>hostname[:port]</i>
16 ] [ -n ] [ -o
17 <i>option=value</i>
18 ]
19 <h2 class="title"><a name="DESCRIPTION">Description</a></h2>
20 <i>cups-lpd</i> is the CUPS Line Printer Daemon ("LPD")
21 mini-server that supports legacy client systems that use the LPD
22 protocol. <i>cups-lpd</i> does not act as a standalone network
23 daemon but instead operates using the Internet "super-server"
24 <i>inetd(8)</i> or <i>xinetd(8)</i>. If you are using <i>inetd</i>,
25 add the following line to the <i>inetd.conf</i> file to enable the
26 <i>cups-lpd</i> mini-server:
27 <br>
28 <pre class="man">
29
30 printer stream tcp nowait lp /usr/lib/cups/daemon/cups-lpd cups-lpd \
31 -o document-format=application/octet-stream
32 </pre>
33 <p><p><b>Note:</b> If you are using Solaris 10 or higher, you must run
34 the <i>inetdconv(1m)</i> program to register the changes to the
35 inetd.conf file.
36 <p>If you are using the newer <i>xinetd(8)</i> daemon, create a file
37 named <i>/etc/xinetd.d/cups</i> containing the following lines:
38 <br>
39 <pre class="man">
40
41 service printer
42 {
43 socket_type = stream
44 protocol = tcp
45 wait = no
46 user = lp
47 group = sys
48 passenv =
49 server = /usr/lib/cups/daemon/cups-lpd
50 server_args = -o document-format=application/octet-stream
51 }
52 </pre>
53 <h2 class="title"><a name="OPTIONS">Options</a></h2>
54 <dl class="man">
55 <dt>-h hostname[:port]
56 <dd style="margin-left: 5.0em"><br>
57 Sets the CUPS server (and port) to use.
58 <dt>-n
59 <dd style="margin-left: 5.0em"><br>
60 Disables reverse address lookups; normally <i>cups-lpd</i> will
61 try to discover the hostname of the client via a reverse DNS
62 lookup.
63 <dt>-o name=value
64 <dd style="margin-left: 5.0em"><br>
65 Inserts options for all print queues. Most often this is used to
66 disable the "l" filter so that remote print jobs are filtered as
67 needed for printing; the examples in the previous section set the
68 "document-format" option to "application/octet-stream" which
69 forces autodetection of the print file format.
70 </dl>
71 <h2 class="title"><a name="PERFORMANCE">Performance</a></h2>
72 <i>cups-lpd</i> performs well with small numbers of clients and
73 printers. However, since a new process is created for each
74 connection and since each process must query the printing system
75 before each job submission, it does not scale to larger
76 configurations. We highly recommend that large configurations
77 use the native IPP support provided by CUPS instead.
78 <h2 class="title"><a name="SECURITY">Security</a></h2>
79 <i>cups-lpd</i> currently does not perform any access control
80 based on the settings in <i>cupsd.conf(5)</i> or in the
81 <i>hosts.allow(5)</i> or <i>hosts.deny(5)</i> files used by TCP
82 wrappers. Therefore, running <i>cups-lpd</i> on your server will
83 allow any computer on your network (and perhaps the entire
84 Internet) to print to your server.
85 <p>While <i>xinetd</i> has built-in access control support, you
86 should use the TCP wrappers package with <i>inetd</i> to limit
87 access to only those computers that should be able to print
88 through your server.
89 <p><i>cups-lpd</i> is not enabled by the standard CUPS distribution.
90 Please consult with your operating system vendor to determine
91 whether it is enabled on your system.
92 <h2 class="title"><a name="COMPATIBILITY">Compatibility</a></h2>
93 <i>cups-lpd</i> does not enforce the restricted source port
94 number specified in RFC 1179, as using restricted ports does not
95 prevent users from submitting print jobs. While this behavior is
96 different than standard Berkeley LPD implementations, it should
97 not affect normal client operations.
98 <p>The output of the status requests follows RFC 2569, Mapping
99 between LPD and IPP Protocols. Since many LPD implementations
100 stray from this definition, remote status reporting to LPD
101 clients may be unreliable.
102 <h2 class="title"><a name="SEE_ALSO">See Also</a></h2>
103 <i>cups(1)</i>, <i>cupsd(8)</i>, <i>inetconv(1m)</i>,
104 <i>inetd(8)</i>, <i>xinetd(8)</i>,
105 <br>
106 <a href="http://localhost:631/help">http://localhost:631/help</a>
107 <h2 class="title"><a name="COPYRIGHT">Copyright</a></h2>
108 Copyright 2007-2013 by Apple Inc.
109
110 </body>
111 </html>