/usr/share/doc/lprng-doc/LPRng-Reference-Multipart/x10288.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 159 160 161 162 163 164 165 166 167 168 169 | <!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>Data File Transfer</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="RFC 1179 - Line Printer Daemon Protocol "
href="rfc1179ref.htm">
<link rel="PREVIOUS" title="Job Transfer " href=
"jobtransfer.htm">
<link rel="NEXT" title="Control File Contents" href="x10324.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=
"jobtransfer.htm" accesskey="P">Prev</a></td>
<td width="80%" align="center" valign="bottom">Chapter 19.
RFC 1179 - Line Printer Daemon Protocol</td>
<td width="10%" align="right" valign="bottom"><a href=
"x10324.htm" accesskey="N">Next</a></td>
</tr>
</table>
<hr align="left" width="100%">
</div>
<div class="SECT1">
<h1 class="SECT1"><a name="AEN10288" id="AEN10288">19.4. Data
File Transfer</a></h1>
<p>As mentioned before a data file is transferred using the
command below.</p>
<div class="INFORMALTABLE">
<a name="AEN10291" id="AEN10291"></a>
<table border="1" frame="border" rules="all" class=
"CALSTABLE">
<col>
<col>
<thead>
<tr>
<th>Command</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>\003nnnn dfname</td>
<td>data file transfer</td>
</tr>
</tbody>
</table>
</div>
<p>From RFC1179: <a name="AEN10302" id="AEN10302"></a></p>
<blockquote class="BLOCKQUOTE">
<p>The data file may contain any 8 bit values at all. The
total number of bytes in the stream may be sent as the first
operand, otherwise the field should be cleared to 0. The name
of the data file should start with ASCII "dfA". This should
be followed by a three digit job number. The job number
should be followed by the host name which has constructed the
data file. Interpretation of the contents of the data file is
determined by the contents of the corresponding control
file.</p>
</blockquote>
<p>There are several surprises in RFC1179.</p>
<ol type="1">
<li>
<p>Apparently a job should only consist of a single data
file. This is a severe limitation, and in fact the BSD
<b class="APPLICATION">lpr</b> and other print spoolers
process jobs with multiple data files. By convention, these
data files have names of the form <tt class=
"LITERAL">dfA</tt>, <tt class="LITERAL">dfB</tt>, ...
<tt class="LITERAL">dfZ</tt>, <tt class="LITERAL">dfa</tt>,
<tt class="LITERAL">dfz</tt>.</p>
</li>
<li>
<p>The RFC does not specify that the control file and data
file job numbers must be identical. Most implementations
follow this convention, which simplifies life
tremendously.</p>
</li>
<li>
<p>The RFC does not specify that the control file and data
file job host names must be identical. Most implementations
follow this convention, which simplifies life
tremendously.</p>
</li>
<li>
<p>A zero length data file does not cause a data transfer
to take place. <b class="APPLICATION">LPRng</b> modifies
this action to be slightly different. When a zero length
data file transfer is indicated, all of the input until the
connection is closed is used as the contents of the data
file.</p>
<p>When <span class="emphasis"><i class=
"EMPHASIS">piping</i></span> into the <b class=
"APPLICATION">lpr</b> program, this can be very useful as
it eliminates the need to create temporary files on the
local host. Note that some print spoolers do not use this
interpretation, and this option should be used
carefully.</p>
</li>
</ol>
</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=
"jobtransfer.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=
"x10324.htm" accesskey="N">Next</a></td>
</tr>
<tr>
<td width="33%" align="left" valign="top">Job Transfer</td>
<td width="34%" align="center" valign="top"><a href=
"rfc1179ref.htm" accesskey="U">Up</a></td>
<td width="33%" align="right" valign="top">Control File
Contents</td>
</tr>
</table>
</div>
<p align="center"></p>
</body>
</html>
|