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