This file is indexed.

/usr/share/doc/lprng-doc/LPRng-Reference-Multipart/reception.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
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
<!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>Job Reception</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="Job Processing" href="jobsteps.htm">
  <link rel="PREVIOUS" title="Submitting Jobs and Service Requests"
  href="submitting.htm">
  <link rel="NEXT" title="Spool Queue Processing " href=
  "spoolq.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=
        "submitting.htm" accesskey="P">Prev</a></td>

        <td width="80%" align="center" valign="bottom">Chapter 15.
        Job Processing</td>

        <td width="10%" align="right" valign="bottom"><a href=
        "spoolq.htm" accesskey="N">Next</a></td>
      </tr>
    </table>
    <hr align="left" width="100%">
  </div>

  <div class="SECT1">
    <h1 class="SECT1"><a name="RECEPTION" id="RECEPTION">15.3. Job
    Reception</a></h1>

    <ul>
      <li>
        <p><tt class="LITERAL">longnumber</tt> FLAG <span class=
        "emphasis"><i class="EMPHASIS">Long job number (6
        digits)</i></span></p>
      </li>

      <li>
        <p><tt class="LITERAL">fifo</tt> FLAG <span class=
        "emphasis"><i class="EMPHASIS">enforce FIFO order for
        reception</i></span></p>
      </li>

      <li>
        <p><tt class="LITERAL">lpd_listen_port=</tt><span class=
        "emphasis"><i class="EMPHASIS"><b class=
        "APPLICATION">lpd</b> will listen on this
        port</i></span></p>
      </li>

      <li>
        <p><tt class=
        "LITERAL">incoming_control_filter=</tt><span class=
        "emphasis"><i class="EMPHASIS">filter to modify incoming
        job control file</i></span></p>
      </li>

      <li>
        <p><tt class=
        "LITERAL">translate_incoming_format=</tt><span class=
        "emphasis"><i class="EMPHASIS">change data file
        formats</i></span></p>
      </li>

      <li>
        <p><tt class=
        "LITERAL">accounting_fixupname=</tt><span class=
        "emphasis"><i class="EMPHASIS">change accounting name
        infomration</i></span></p>
      </li>
    </ul>

    <p>When a print job is received, the <b class=
    "APPLICATION">lpd</b> server will assign a job number to the
    new job. Historically these have been in the range of 0 to 999,
    but the <tt class="LITERAL">longnumber</tt> option allows
    numbers from 0 to 999,999 to be assigned. The server then
    checks to see that all of the data files for a job have been
    transferred correctly.</p>

    <p>The <tt class="LITERAL">fifo</tt> flag forces all jobs
    receieved from a particular host to be processed in First In,
    First Out (fifo) order. No new jobs will be processed until the
    incoming job has been released into the spool queue.</p>

    <p>If an incoming control file filter is specified, then the
    incoming job's control file will be passed through the
    <tt class="LITERAL">incoming_control_filter</tt> filter if it
    is specified. This allows the modification of the control
    file.</p>

    <p>The majority of control file modifications are simple job
    file format changes. The <tt class=
    "LITERAL">translate_incoming_format</tt> option provides a
    simple way to do this. See the <span class="emphasis"><i class=
    "EMPHASIS"><a href=
    "translateformat.htm">translate_format</a></i></span> for
    details.</p>

    <p>The <tt class="LITERAL">accounting_namefixup</tt> option was
    introduced to allow a simple mapping of host and user names to
    names to be used for accounting purposes. By convention, the
    <tt class="LITERAL">R</tt> field in the job control file
    specifies the name to be used for accounting purposes.</p>

    <div class="INFORMALEXAMPLE">
      <a name="AEN6990" id="AEN6990"></a>
      <pre class="SCREEN">
accounting_namefixup=list[,list]*
   where list is:   host(,host*)[=user(,user*)]
</pre>
    </div>The incoming job is checked to see if the originating
    host is in the list of hosts; the first matching one found is
    used.

    <p>Each host list has the format: host,host... where host has
    the same format used for the <tt class="LITERAL">oh</tt> and
    other host name matching options. You can use '!host' to invert
    matching. For example: <tt class=
    "LITERAL">host1,127.*,!somehost</tt>.</p>

    <p>When a host match is found, the name to be used for the user
    is determined from the user list; if none is specified then no
    changes are made. Each entry in the user list has the format
    <tt class="LITERAL">${option}</tt> or <tt class=
    "LITERAL">name</tt>; the <tt class="LITERAL">${option}</tt>
    values are extracted from the control file (capital letters) or
    printcap/configuration information (lower case letters/names).
    The first non-empty value list value used. For example, the
    <tt class="LITERAL">${R},${L},${accounting_name},anon</tt> will
    select the control file 'R' option value, then the 'L' option
    value, then the printcap/config option 'accounting_name' value,
    and then finally the 'anon' value.</p>

    <p>The control file is then passed through the <tt class=
    "LITERAL">router</tt> routing filter. This allows the incoming
    job to be redirected to one or more print queues. For details
    about all of the capabilities of the routing filter, see
    <a href="destinations.htm">Dynamic Routing</a>.</p>

    <p>Finally, the <b class="APPLICATION">lpd</b> server is
    requested to start a spooling process that will print the newly
    arrived job.</p>
  </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=
        "submitting.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=
        "spoolq.htm" accesskey="N">Next</a></td>
      </tr>

      <tr>
        <td width="33%" align="left" valign="top">Submitting Jobs
        and Service Requests</td>

        <td width="34%" align="center" valign="top"><a href=
        "jobsteps.htm" accesskey="U">Up</a></td>

        <td width="33%" align="right" valign="top">Spool Queue
        Processing</td>
      </tr>
    </table>
  </div>

  <p align="center"></p>
</body>
</html>