/usr/share/doc/lprng-doc/LPRng-Reference-Multipart/x5205.htm is in lprng-doc 3.8.A~rc2-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta name="generator" content=
"HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
<title>Problems With Network Print Servers</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
<link rel="HOME" title=" LPRng Reference Manual" href=
"index.htm">
<link rel="UP" title="Printer Communication and Protocols " href=
"printercomm.htm">
<link rel="PREVIOUS" title="HP JetDirect Interface" href=
"x5169.htm">
<link rel="NEXT" title="Printing to a SMB (MicroSoft) Printer"
href="x5236.htm">
</head>
<body class="SECT1" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#840084" alink="#0000FF">
<div class="NAVHEADER">
<table summary="Header navigation table" width="100%" border=
"0" cellpadding="0" cellspacing="0">
<tr>
<th colspan="3" align="center">LPRng Reference Manual: 24
Sep 2004 (For LPRng-3.8.28)</th>
</tr>
<tr>
<td width="10%" align="left" valign="bottom"><a href=
"x5169.htm" accesskey="P">Prev</a></td>
<td width="80%" align="center" valign="bottom">Chapter 11.
Printer Communication and Protocols</td>
<td width="10%" align="right" valign="bottom"><a href=
"x5236.htm" accesskey="N">Next</a></td>
</tr>
</table>
<hr align="left" width="100%">
</div>
<div class="SECT1">
<h1 class="SECT1"><a name="AEN5205" id="AEN5205">11.8. Problems
With Network Print Servers</a></h1>
<p>Most of the Network Print Servers are implemented using
extremely simply software. The following is a list of some
problems and what options the <b class="APPLICATION">LPRng</b>
software uses to handle them.</p>
<div class="SECT2">
<h2 class="SECT2"><a name="AEN5209" id="AEN5209">11.8.1.
Network Print Server Not Responding</a></h2>
<p>Only a single TCP/IP connection is accepted at a time.
This means that when one user is sending a job then the unit
will not accept other connections. There is another side
effect of this problem, which is that some implementations
will accept a network connection but not read any data from
the connection until the previous connection is finished.</p>
<p>The deal with these problems the <tt class=
"LITERAL">connect_timeout</tt>, <tt class=
"LITERAL">send_job_rw_timeout</tt>, and <tt class=
"LITERAL">send_query_rw_timeout</tt> are used to control job
transfer and lpq status gathering. See <a href=
"printingjob.htm">Printing Job Files</a> and <a href=
"opendevice.htm">Opening the Output Device</a> for
details.</p>
</div>
<div class="SECT2">
<h2 class="SECT2"><a name="AEN5218" id="AEN5218">11.8.2.
Network Print Server Does Not Handle LPQ, LPRM</a></h2>
<p>Some Network Print Servers do not respond to <tt class=
"LITERAL">lpq</tt> or <tt class="LITERAL">lprm</tt> queries
correctly. The <tt class="LITERAL">remote_support</tt> option
can be used to solve this problem by specifying what
operations the remote print server can handle:</p>
<div class="INFORMALEXAMPLE">
<a name="AEN5224" id="AEN5224"></a>
<pre class="SCREEN">
:remote_support=RMQVC
R = lpr, M = lprmg, Q = lpq, V = lpq -v, C = lpc
:remote_support=R # printer only handles LPR
</pre>
</div>
</div>
<div class="SECT2">
<h2 class="SECT2"><a name="AEN5226" id="AEN5226">11.8.3.
Incomplete Job Transfers</a></h2>
<p>This is the result of a defective or buggy TCP/IP stacks.
A common problem is the habit that some Network Print Servers
occaisionally discard data at the end of a print job when a
network connection is <span class="emphasis"><i class=
"EMPHASIS">half-closed</i></span>. A <span class=
"emphasis"><i class="EMPHASIS">half-closed</i></span>
connection is one where one end of the sending connection
indicates that no further data will be sent. Unfortunately,
the Network Print Server will then try to close the
connection in the other direction. When this does not
immediately succeed, it will terminate the network
connection, discarding any unprinted data.</p>
<p>The <tt class="LITERAL">half_close</tt> flag can be used
to solve this problem. See <a href="normalterm.htm">Normal
Termination</a> for more details.</p>
<div class="INFORMALEXAMPLE">
<a name="AEN5234" id="AEN5234"></a>
<pre class="SCREEN">
lp:lp=lp@remote # shutdown(fd,WRITE) connection, wait for end
lp:lp=lp@remote:half_close@ # close() connection and do not wait
</pre>
</div>
</div>
</div>
<div class="NAVFOOTER">
<hr align="left" width="100%">
<table summary="Footer navigation table" width="100%" border=
"0" cellpadding="0" cellspacing="0">
<tr>
<td width="33%" align="left" valign="top"><a href=
"x5169.htm" accesskey="P">Prev</a></td>
<td width="34%" align="center" valign="top"><a href=
"index.htm" accesskey="H">Home</a></td>
<td width="33%" align="right" valign="top"><a href=
"x5236.htm" accesskey="N">Next</a></td>
</tr>
<tr>
<td width="33%" align="left" valign="top">HP JetDirect
Interface</td>
<td width="34%" align="center" valign="top"><a href=
"printercomm.htm" accesskey="U">Up</a></td>
<td width="33%" align="right" valign="top">Printing to a
SMB (MicroSoft) Printer</td>
</tr>
</table>
</div>
<p align="center"></p>
</body>
</html>
|