[thirdparty/cups.git] / doc / help / man-cups-lpd.html

<!DOCTYPE HTML>
<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 class="man">

    printer stream tcp nowait lp /usr/lib/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 class="man">

    service printer
    {
        socket_type = stream
        protocol = tcp
        wait = no
        user = lp
	group = sys
	passenv =
        server = /usr/lib/cups/daemon/cups-lpd
	server_args = -o document-format=application/octet-stream
    }
</pre>
<h2 class="title"><a name="OPTIONS">Options</a></h2>
<dl class="man">
<dt>-h hostname[:port]
<dd style="margin-left: 5.0em"><br>
Sets the CUPS server (and port) to use.
<dt>-n
<dd style="margin-left: 5.0em"><br>
Disables reverse address lookups; normally <i>cups-lpd</i> will
try to discover the hostname of the client via a reverse DNS
lookup.
<dt>-o name=value
<dd style="margin-left: 5.0em"><br>
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.
</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 <i>cupsd.conf(5)</i> 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>, <i>cupsd(8)</i>, <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
c277f98c	1	<!DOCTYPE HTML>
94436c5a MS	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>
c277f98c MS	13	<b>cups-lpd</b>
	14	[ -h
	15	<i>hostname[:port]</i>
	16	] [ -n ] [ -o
	17	<i>option=value</i>
	18	]
94436c5a MS	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>
2909c66c	28	<pre class="man">
94436c5a	29
ffa2ca90	30	printer stream tcp nowait lp /usr/lib/cups/daemon/cups-lpd cups-lpd \
94436c5a MS	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>
2909c66c	39	<pre class="man">
94436c5a MS	40
	41	service printer
	42	{
	43	socket_type = stream
	44	protocol = tcp
	45	wait = no
	46	user = lp
	47	group = sys
	48	passenv =
ffa2ca90	49	server = /usr/lib/cups/daemon/cups-lpd
94436c5a MS	50	server_args = -o document-format=application/octet-stream
	51	}
	52	</pre>
	53	<h2 class="title"><a name="OPTIONS">Options</a></h2>
2909c66c MS	54	<dl class="man">
	55	<dt>-h hostname[:port]
	56	<dd style="margin-left: 5.0em"><br>
c277f98c	57	Sets the CUPS server (and port) to use.
2909c66c MS	58	<dt>-n
2909c66c MS	59	<dd style="margin-left: 5.0em"><br>
c277f98c	60	Disables reverse address lookups; normally <i>cups-lpd</i> will
94436c5a MS	61	try to discover the hostname of the client via a reverse DNS
94436c5a MS	62	lookup.
2909c66c MS	63	<dt>-o name=value
2909c66c MS	64	<dd style="margin-left: 5.0em"><br>
c277f98c	65	Inserts options for all print queues. Most often this is used to
94436c5a MS	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.
2909c66c	70	</dl>
94436c5a MS	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
c277f98c	80	based on the settings in <i>cupsd.conf(5)</i> or in the
94436c5a MS	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>
c277f98c	103	<i>cups(1)</i>, <i>cupsd(8)</i>, <i>inetconv(1m)</i>,
94436c5a MS	104	<i>inetd(8)</i>, <i>xinetd(8)</i>,
94436c5a MS	105	<br>
c277f98c	106	<a href="http://localhost:631/help">http://localhost:631/help</a>
94436c5a MS	107	<h2 class="title"><a name="COPYRIGHT">Copyright</a></h2>
	108	Copyright 2007-2013 by Apple Inc.
	109
	110	</body>
	111	</html>