[thirdparty/cups.git] / doc / help / 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 using the Internet "super-server"
<i>inetd(8)</i> or <i>xinetd(8)</i>. If you are using <i>inetd</i>,
add the following line to the <i>inetd.conf</i> file to enable the
<i>cups-lpd</i> mini-server:
<br>
<pre>

    printer stream tcp nowait lp /usr/libexec/cups/daemon/cups-lpd cups-lpd \
        -o document-format=application/octet-stream
</pre>
<p><p><b>Note:</b> If you are using Solaris 10 or higher, you must run
the <i>inetdconv(1m)</i> program to register the changes to the
inetd.conf file.
<p>If you are using the newer <i>xinetd(8)</i> daemon, create a file
named <i>/etc/xinetd.d/cups</i> containing the following lines:
<br>
<pre>

    service printer
    {
        socket_type = stream
        protocol = tcp
        wait = no
        user = lp
	group = sys
	passenv =
        server = /usr/libexec/cups/daemon/cups-lpd
	server_args = -o document-format=application/octet-stream
    }
</pre>
<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>While <i>xinetd</i> has built-in access control support, you
should use the TCP wrappers package with <i>inetd</i> to limit
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="SEE_ALSO">See Also</a></h2>
<i>cups(1)</i>, <a href='man-cupsd.html?TOPIC=Man+Pages'>cupsd(8)</a>, <i>inetconv(1m)</i>,
<i>inetd(8)</i>, <i>xinetd(8)</i>,
<br>
<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>
Commit	Line	Data
62b97abe	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
	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
	14	</b>[ -h
	15	<i>hostname[:port]
	16	</i>] [ -n ] [ -o
	17	<i>option=value
	18	</i>]
	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>
	29
579b6de1	30	printer stream tcp nowait lp /usr/libexec/cups/daemon/cups-lpd cups-lpd \
62b97abe	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>
	40
	41	service printer
	42	{
	43	socket_type = stream
	44	protocol = tcp
	45	wait = no
	46	user = lp
	47	group = sys
	48	passenv =
579b6de1	49	server = /usr/libexec/cups/daemon/cups-lpd
62b97abe	50	server_args = -o document-format=application/octet-stream
	51	}
	52	</pre>
	53	<h2 class="title"><a name="OPTIONS">Options</a></h2>
	54	<dl>
	55	<dt>-h hostname[:port]
	56	</dt>
	57	<dd></dd>
	58	<dd>Sets the CUPS server (and port) to use.
	59	</dd>
	60	<dt>-n
	61	</dt>
	62	<dd></dd>
	63	<dd>Disables reverse address lookups; normally <i>cups-lpd</i> will
	64	try to discover the hostname of the client via a reverse DNS
	65	lookup.
	66	</dd>
	67	<dt>-o name=value
	68	</dt>
	69	<dd></dd>
	70	<dd>Inserts options for all print queues. Most often this is used to
	71	disable the "l" filter so that remote print jobs are filtered as
	72	needed for printing; the examples in the previous section set the
	73	"document-format" option to "application/octet-stream" which
	74	forces autodetection of the print file format.
	75	</dd>
	76	</dl>
	77	<h2 class="title"><a name="PERFORMANCE">Performance</a></h2>
	78	<i>cups-lpd</i> performs well with small numbers of clients and
	79	printers. However, since a new process is created for each
	80	connection and since each process must query the printing system
	81	before each job submission, it does not scale to larger
	82	configurations. We highly recommend that large configurations
	83	use the native IPP support provided by CUPS instead.
	84	<h2 class="title"><a name="SECURITY">Security</a></h2>
	85	<i>cups-lpd</i> currently does not perform any access control
	86	based on the settings in <a href='man-cupsd.conf.html?TOPIC=Man+Pages'>cupsd.conf(5)</a> or in the
	87	<i>hosts.allow(5)</i> or <i>hosts.deny(5)</i> files used by TCP
	88	wrappers. Therefore, running <i>cups-lpd</i> on your server will
	89	allow any computer on your network (and perhaps the entire
	90	Internet) to print to your server.
	91	<p>While <i>xinetd</i> has built-in access control support, you
	92	should use the TCP wrappers package with <i>inetd</i> to limit
	93	access to only those computers that should be able to print
	94	through your server.
	95	<p><i>cups-lpd</i> is not enabled by the standard CUPS distribution.
	96	Please consult with your operating system vendor to determine
	97	whether it is enabled on your system.
	98	<h2 class="title"><a name="COMPATIBILITY">Compatibility</a></h2>
	99	<i>cups-lpd</i> does not enforce the restricted source port
	100	number specified in RFC 1179, as using restricted ports does not
	101	prevent users from submitting print jobs. While this behavior is
	102	different than standard Berkeley LPD implementations, it should
	103	not affect normal client operations.
	104	<p>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	<h2 class="title"><a name="SEE_ALSO">See Also</a></h2>
	109	<i>cups(1)</i>, <a href='man-cupsd.html?TOPIC=Man+Pages'>cupsd(8)</a>, <i>inetconv(1m)</i>,
	110	<i>inetd(8)</i>, <i>xinetd(8)</i>,
	111	<br>
	112	<a href='http://localhost:631/help'>http://localhost:631/help</a>
	113	<h2 class="title"><a name="COPYRIGHT">Copyright</a></h2>
114	Copyright 2007-2013 by Apple Inc.
115
116	</body>
117	</html>