]> git.ipfire.org Git - thirdparty/cups.git/blob - man/cups-lpd.man
Load cups into easysw/current.
[thirdparty/cups.git] / man / cups-lpd.man
1 .\"
2 .\" "$Id: cups-lpd.man 4867 2005-12-03 15:45:53Z mike $"
3 .\"
4 .\" cups-lpd man page for the Common UNIX Printing System (CUPS).
5 .\"
6 .\" Copyright 1997-2005 by Easy Software Products.
7 .\"
8 .\" These coded instructions, statements, and computer programs are the
9 .\" property of Easy Software Products and are protected by Federal
10 .\" copyright law. Distribution and use rights are outlined in the file
11 .\" "LICENSE.txt" which should have been included with this file. If this
12 .\" file is missing or damaged please contact Easy Software Products
13 .\" at:
14 .\"
15 .\" Attn: CUPS Licensing Information
16 .\" Easy Software Products
17 .\" 44141 Airport View Drive, Suite 204
18 .\" Hollywood, Maryland 20636 USA
19 .\"
20 .\" Voice: (301) 373-9600
21 .\" EMail: cups-info@cups.org
22 .\" WWW: http://www.cups.org
23 .\"
24 .TH cups-lpd 8 "Common UNIX Printing System" "3 December 2005" "Easy Software Products"
25 .SH NAME
26 cups-lpd \- receive print jobs and report printer status to lpd clients
27 .SH SYNOPSIS
28 .B cups-lpd
29 [ -o
30 .I option=value
31 ]
32 .SH DESCRIPTION
33 \fBcups-lpd\fR is the CUPS Line Printer Daemon ("LPD") mini-server that
34 supports legacy client systems that use the LPD protocol.
35 \fBcups-lpd\fR does not act as a standalone network daemon but instead
36 operates using the Internet "super-server" \fBinetd(8)\fR. Add the
37 following line to the \fBinetd.conf\fR file to enable the
38 \fBcups-lpd\fR daemon:
39 .br
40 .nf
41
42 printer stream tcp nowait lp /path/to/cups/daemon/cups-lpd cups-lpd \\
43 -o document-format=application/octet-stream
44 .fi
45 .LP
46 If you are using the newer \fIxinetd(8)\fR daemon, add the following
47 lines to the \fBxinetd.conf\fR file:
48 .br
49 .nf
50
51 service printer
52 {
53 socket_type = stream
54 protocol = tcp
55 wait = no
56 user = lp
57 group = sys
58 passenv =
59 server = /path/to/cups/daemon/cups-lpd
60 server_args = -o document-format=application/octet-stream
61 }
62 .fi
63 .LP
64 The /path/to/cups/daemon is usually /usr/lib/cups/daemon or
65 /usr/libexec/cups/daemon, depending on the operating system.
66 Consult the cupsd.conf file for the local setting.
67 .SH OPTIONS
68 The \fI-o\fR option to \fBcups-lpd\fR inserts options for all
69 print queues. Most often this is used to disable the "l" filter
70 so that remote print jobs are filtered as needed for printing;
71 the examples in the previous section set the "document-format"
72 option to "application/octet-stream" which forces autodetection
73 of the print file format.
74 .SH PERFORMANCE
75 \fBcups-lpd\fR performs well with small numbers of clients and
76 printers. However, since a new process is created for each
77 connection and since each process must query the printing system
78 before each job submission, it does not scale to larger
79 configurations. We highly recommend that large configurations
80 use the native IPP support provided by CUPS instead.
81 .SH SECURITY
82 \fBcups-lpd\fR currently does not perform any access control
83 based on the settings in \fIcupsd.conf(5)\fR or in the
84 \fIhosts.allow(5)\fR or \fIhosts.deny\fR files used by TCP
85 wrappers. Therefore, running \fBcups-lpd\fR on your server will
86 allow any computer on your network (and perhaps the entire
87 Internet) to print to your server.
88 .LP
89 While \fIxinetd\fR has built-in access control support, you
90 should use the TCP wrappers package with \fIinetd\fR to limit
91 access to only those computers that should be able to print
92 through your server.
93 .LP
94 \fBcups-lpd\fR is not enabled by the standard CUPS distribution.
95 Please consult with your operating system vendor to determine
96 whether it is enabled in their distribution.
97 .SH COMPATIBILITY
98 \fBcups-lpd\fR does not enforce the restricted source port
99 number specified in RFC 1179, as using restricted ports does not
100 prevent users from submitting print jobs. While this behavior is
101 different than standard Berkeley LPD implementations, it should
102 not affect normal client operations.
103 .LP
104 The output of the status requests follows RFC 2569, Mapping
105 between LPD and IPP Protocols. Since many LPD implementations
106 stray from this definition, remote status reporting to LPD
107 clients may be unreliable.
108 .SH SEE ALSO
109 cups(1), cupsd(8), inetd(8), xinetd(8)
110 .SH COPYRIGHT
111 Copyright 1993-2005 by Easy Software Products, All Rights Reserved.
112 .\"
113 .\" End of "$Id: cups-lpd.man 4867 2005-12-03 15:45:53Z mike $".
114 .\"