• Home
  • History
  • Annotate
  • Line#
  • Navigate
  • Raw
  • Download
  • only in /asuswrt-rt-n18u-9.0.0.4.380.2695/release/src/router/LPRng/DOCS/LPRng-Reference-Multipart/
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2
3<html>
4  <head>
5    <meta name="generator" content="HTML Tidy, see www.w3.org">
6    <title>Job Reception</title>
7    <meta name="GENERATOR" content=
8    "Modular DocBook HTML Stylesheet Version 1.7">
9    <link rel="HOME" title=" LPRng Reference Manual" href=
10    "index.htm">
11    <link rel="UP" title="Job Processing" href="jobsteps.htm">
12    <link rel="PREVIOUS" title=
13    "Submitting Jobs and Service Requests" href="submitting.htm">
14    <link rel="NEXT" title="Spool Queue Processing " href=
15    "spoolq.htm">
16  </head>
17
18  <body class="SECT1" bgcolor="#FFFFFF" text="#000000" link=
19  "#0000FF" vlink="#840084" alink="#0000FF">
20    <div class="NAVHEADER">
21      <table summary="Header navigation table" width="100%" border=
22      "0" cellpadding="0" cellspacing="0">
23        <tr>
24          <th colspan="3" align="center">LPRng Reference Manual: 5
25          Sep 2003 (For LPRng-3.8.22)</th>
26        </tr>
27
28        <tr>
29          <td width="10%" align="left" valign="bottom"><a href=
30          "submitting.htm" accesskey="P">Prev</a></td>
31
32          <td width="80%" align="center" valign="bottom">Chapter
33          15. Job Processing</td>
34
35          <td width="10%" align="right" valign="bottom"><a href=
36          "spoolq.htm" accesskey="N">Next</a></td>
37        </tr>
38      </table>
39      <hr align="LEFT" width="100%">
40    </div>
41
42    <div class="SECT1">
43      <h1 class="SECT1"><a name="RECEPTION">15.3. Job
44      Reception</a></h1>
45
46      <ul>
47        <li>
48          <p><var class="LITERAL">longnumber</var> FLAG <span
49          class="emphasis"><i class="EMPHASIS">Long job number (6
50          digits)</i></span></p>
51        </li>
52
53        <li>
54          <p><var class="LITERAL">fifo</var> FLAG <span class=
55          "emphasis"><i class="EMPHASIS">enforce FIFO order for
56          reception</i></span></p>
57        </li>
58
59        <li>
60          <p><var class="LITERAL">lpd_listen_port=</var><span
61          class="emphasis"><i class="EMPHASIS"><b class=
62          "APPLICATION">lpd</b> will listen on this
63          port</i></span></p>
64        </li>
65
66        <li>
67          <p><var class=
68          "LITERAL">incoming_control_filter=</var><span class=
69          "emphasis"><i class="EMPHASIS">filter to modify incoming
70          job control file</i></span></p>
71        </li>
72
73        <li>
74          <p><var class=
75          "LITERAL">translate_incoming_format=</var><span class=
76          "emphasis"><i class="EMPHASIS">change data file
77          formats</i></span></p>
78        </li>
79
80        <li>
81          <p><var class="LITERAL">accounting_fixupname=</var><span
82          class="emphasis"><i class="EMPHASIS">change accounting
83          name infomration</i></span></p>
84        </li>
85      </ul>
86
87      <p>When a print job is received, the <b class=
88      "APPLICATION">lpd</b> server will assign a job number to the
89      new job. Historically these have been in the range of 0 to
90      999, but the <var class="LITERAL">longnumber</var> option
91      allows numbers from 0 to 999,999 to be assigned. The server
92      then checks to see that all of the data files for a job have
93      been transferred correctly.</p>
94
95      <p>The <var class="LITERAL">fifo</var> flag forces all jobs
96      receieved from a particular host to be processed in First In,
97      First Out (fifo) order. No new jobs will be processed until
98      the incoming job has been released into the spool queue.</p>
99
100      <p>If an incoming control file filter is specified, then the
101      incoming job's control file will be passed through the <var
102      class="LITERAL">incoming_control_filter</var> filter if it is
103      specified. This allows the modification of the control
104      file.</p>
105
106      <p>The majority of control file modifications are simple job
107      file format changes. The <var class=
108      "LITERAL">translate_incoming_format</var> option provides a
109      simple way to do this. See the <span class="emphasis"><i
110      class="EMPHASIS"><a href=
111      "translateformat.htm">translate_format</a></i></span> for
112      details.</p>
113
114      <p>The <var class="LITERAL">accounting_namefixup</var> option
115      was introduced to allow a simple mapping of host and user
116      names to names to be used for accounting purposes. By
117      convention, the <var class="LITERAL">R</var> field in the job
118      control file specifies the name to be used for accounting
119      purposes.</p>
120
121      <div class="INFORMALEXAMPLE">
122        <a name="AEN6959"></a>
123<pre class="SCREEN">
124    accounting_namefixup=list[,list]*
125       where list is:   host(,host*)[=user(,user*)]
126</pre>
127      </div>
128      The incoming job is checked to see if the originating host is
129      in the list of hosts; the first matching one found is
130      used.<br>
131      <br>
132
133      <p>Each host list has the format: host,host... where host has
134      the same format used for the <var class="LITERAL">oh</var>
135      and other host name matching options. You can use '!host' to
136      invert matching. For example: <var class=
137      "LITERAL">host1,127.*,!somehost</var>.</p>
138
139      <p>When a host match is found, the name to be used for the
140      user is determined from the user list; if none is specified
141      then no changes are made. Each entry in the user list has the
142      format <var class="LITERAL">${option}</var> or <var class=
143      "LITERAL">name</var>; the <var class=
144      "LITERAL">${option}</var> values are extracted from the
145      control file (capital letters) or printcap/configuration
146      information (lower case letters/names). The first non-empty
147      value list value used. For example, the <var class=
148      "LITERAL">${R},${L},${accounting_name},anon</var> will select
149      the control file 'R' option value, then the 'L' option value,
150      then the printcap/config option 'accounting_name' value, and
151      then finally the 'anon' value.</p>
152
153      <p>The control file is then passed through the <var class=
154      "LITERAL">router</var> routing filter. This allows the
155      incoming job to be redirected to one or more print queues.
156      For details about all of the capabilities of the routing
157      filter, see <a href="destinations.htm">Dynamic
158      Routing</a>.</p>
159
160      <p>Finally, the <b class="APPLICATION">lpd</b> server is
161      requested to start a spooling process that will print the
162      newly arrived job.</p>
163    </div>
164
165    <div class="NAVFOOTER">
166      <hr align="LEFT" width="100%">
167
168      <table summary="Footer navigation table" width="100%" border=
169      "0" cellpadding="0" cellspacing="0">
170        <tr>
171          <td width="33%" align="left" valign="top"><a href=
172          "submitting.htm" accesskey="P">Prev</a></td>
173
174          <td width="34%" align="center" valign="top"><a href=
175          "index.htm" accesskey="H">Home</a></td>
176
177          <td width="33%" align="right" valign="top"><a href=
178          "spoolq.htm" accesskey="N">Next</a></td>
179        </tr>
180
181        <tr>
182          <td width="33%" align="left" valign="top">Submitting Jobs
183          and Service Requests</td>
184
185          <td width="34%" align="center" valign="top"><a href=
186          "jobsteps.htm" accesskey="U">Up</a></td>
187
188          <td width="33%" align="right" valign="top">Spool Queue
189          Processing</td>
190        </tr>
191      </table>
192    </div>
193  </body>
194</html>
195
196