This file is indexed.

/usr/share/doc/lprng-doc/LPRng-Reference-Multipart/loadbalance.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
<!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>Printer Load Balancing</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="Printcap Database " href="printcapref.htm">
  <link rel="PREVIOUS" title="Dynamic Routing " href=
  "destinations.htm">
  <link rel="NEXT" title="Locations of Printcap Files " href=
  "printcappath.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=
        "destinations.htm" accesskey="P">Prev</a></td>

        <td width="80%" align="center" valign="bottom">Chapter 12.
        Printcap Database</td>

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

  <div class="SECT1">
    <h1 class="SECT1"><a name="LOADBALANCE" id="LOADBALANCE">12.14.
    Printer Load Balancing</a></h1>

    <p>Options used:</p>

    <ul>
      <li>
        <p><tt class="LITERAL">ss=</tt><span class=
        "emphasis"><i class="EMPHASIS">queue served by
        printer</i></span></p>
      </li>

      <li>
        <p><tt class="LITERAL">sv=</tt><span class=
        "emphasis"><i class="EMPHASIS">printers where jobs are sent
        (servers)</i></span></p>
      </li>
    </ul>

    <p>In a large site, you could have several equivalent printers,
    which will be used by many people. The reason for this is, of
    course, to increase the printer output by enabling several jobs
    to be printed at once. A load balance print queue is one that
    feeds jobs to other queues and has a <tt class=
    "LITERAL">sv=q1,q2,...</tt> printcap entry that specifies the
    destination or server queues. These must be print queue entries
    and have spool directories on the server.</p>

    <p>The service queues have a <tt class=
    "LITERAL">ss=</tt><span class="emphasis"><i class=
    "EMPHASIS">mainqueue</i></span> printcap entry This informs the
    <b class="APPLICATION">lpd</b> server that the queue operates
    under the control of the <span class="emphasis"><i class=
    "EMPHASIS">mainqueue</i></span> print queue, and is fed jobs
    from it.</p>

    <p>During normal operation, when the <b class=
    "APPLICATION">lpd</b> server has a job to print in the
    <span class="emphasis"><i class=
    "EMPHASIS">mainqueue</i></span>, it will check to see if there
    is an idle <span class="emphasis"><i class=
    "EMPHASIS">service</i></span> queue. If there is, it will
    transfer the job to the service queue spooling directory and
    start the service queue printing activities.</p>

    <p>Even though the queues are not meant for direct use, people
    can print directly to individual queues. This allows a specific
    load sharing printer to be used. If you wanted to <span class=
    "emphasis"><i class="EMPHASIS">hide</i></span> the load sharing
    printers, i.e. - not allow direct spooling to them, then you
    would simply remove the non-server entries from the
    printcap.</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=
        "destinations.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=
        "printcappath.htm" accesskey="N">Next</a></td>
      </tr>

      <tr>
        <td width="33%" align="left" valign="top">Dynamic
        Routing</td>

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

        <td width="33%" align="right" valign="top">Locations of
        Printcap Files</td>
      </tr>
    </table>
  </div>

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