]> git.ipfire.org Git - thirdparty/cups.git/blob - man/cups-lpd.man.in
Load cups into easysw/current.
[thirdparty/cups.git] / man / cups-lpd.man.in
1 .\"
2 .\" "$Id: cups-lpd.man.in 5099 2006-02-13 02:46:10Z mike $"
3 .\"
4 .\" cups-lpd man page for the Common UNIX Printing System (CUPS).
5 .\"
6 .\" Copyright 1997-2006 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" "12 Febrary 2006" "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 \fIcups-lpd\fR is the CUPS Line Printer Daemon ("LPD")
34 mini-server that supports legacy client systems that use the LPD
35 protocol. \fIcups-lpd\fR does not act as a standalone network
36 daemon but instead operates using the Internet "super-server"
37 \fIinetd(8)\fR or \fIxinetd(8)\fR. If you are using \fIinetd\fR,
38 add the following line to the \fIinetd.conf\fR file to enable the
39 \fIcups-lpd\fR mini-server:
40 .br
41 .nf
42
43 printer stream tcp nowait lp @CUPS_SERVERBIN@/daemon/cups-lpd cups-lpd \\
44 -o document-format=application/octet-stream
45 .fi
46 .LP
47 If you are using the newer \fIxinetd(8)\fR daemon, create a file
48 named \fI/etc/xinetd.d/cups\fR containing the following lines:
49 .br
50 .nf
51
52 service printer
53 {
54 socket_type = stream
55 protocol = tcp
56 wait = no
57 user = lp
58 group = sys
59 passenv =
60 server = @CUPS_SERVERBIN@/daemon/cups-lpd
61 server_args = -o document-format=application/octet-stream
62 }
63 .fi
64 .SH OPTIONS
65 .TP 5
66 -o name=value
67 .br
68 Inserts options for all print queues. Most often this is used to
69 disable the "l" filter so that remote print jobs are filtered as
70 needed for printing; the examples in the previous section set the
71 "document-format" option to "application/octet-stream" which
72 forces autodetection of the print file format.
73 .SH PERFORMANCE
74 \fIcups-lpd\fR performs well with small numbers of clients and
75 printers. However, since a new process is created for each
76 connection and since each process must query the printing system
77 before each job submission, it does not scale to larger
78 configurations. We highly recommend that large configurations
79 use the native IPP support provided by CUPS instead.
80 .SH SECURITY
81 \fIcups-lpd\fR currently does not perform any access control
82 based on the settings in \fIcupsd.conf(5)\fR or in the
83 \fIhosts.allow(5)\fR or \fIhosts.deny(5)\fR files used by TCP
84 wrappers. Therefore, running \fIcups-lpd\fR on your server will
85 allow any computer on your network (and perhaps the entire
86 Internet) to print to your server.
87 .LP
88 While \fIxinetd\fR has built-in access control support, you
89 should use the TCP wrappers package with \fIinetd\fR to limit
90 access to only those computers that should be able to print
91 through your server.
92 .LP
93 \fIcups-lpd\fR is not enabled by the standard CUPS distribution.
94 Please consult with your operating system vendor to determine
95 whether it is enabled on your system.
96 .SH COMPATIBILITY
97 \fIcups-lpd\fR does not enforce the restricted source port
98 number specified in RFC 1179, as using restricted ports does not
99 prevent users from submitting print jobs. While this behavior is
100 different than standard Berkeley LPD implementations, it should
101 not affect normal client operations.
102 .LP
103 The output of the status requests follows RFC 2569, Mapping
104 between LPD and IPP Protocols. Since many LPD implementations
105 stray from this definition, remote status reporting to LPD
106 clients may be unreliable.
107 .SH SEE ALSO
108 \fIcups(1)\fR, \fIcupsd(8)\fR, \fIinetd(8)\fR, \fIxinetd(8)\fR,
109 .br
110 http://localhost:631/help
111 .SH COPYRIGHT
112 Copyright 1997-2006 by Easy Software Products, All Rights Reserved.
113 .\"
114 .\" End of "$Id: cups-lpd.man.in 5099 2006-02-13 02:46:10Z mike $".
115 .\"