File: secoh.htm

package info (click to toggle)
lprng 3.8.10-1.2
  • links: PTS
  • area: main
  • in suites: woody
  • size: 13,076 kB
  • ctags: 4,348
  • sloc: ansic: 35,394; sh: 10,756; perl: 2,210; makefile: 1,046
file content (124 lines) | stat: -rw-r--r-- 4,696 bytes parent folder | download
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
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta name="generator" content="HTML Tidy, see www.w3.org">
    <title>Single Printcap File for Large Installation</title>
    <meta name="GENERATOR" content=
    "Modular DocBook HTML Stylesheet Version 1.71 ">
    <link rel="HOME" title=" LPRng-HOWTO" href="index.htm">
    <link rel="UP" title="Printcap Database " href=
    "printcapref.htm">
    <link rel="PREVIOUS" title="Locations of Printcap Files " href=
    "printcappath.htm">
    <link rel="NEXT" title=
    "Management Strategies for Large Installations" href=
    "x6065.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-HOWTO: 1 Apr 2002
          (For LPRng-3.8.10)</th>
        </tr>

        <tr>
          <td width="10%" align="left" valign="bottom"><a href=
          "printcappath.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=
          "x6065.htm" accesskey="N">Next</a></td>
        </tr>
      </table>
      <hr align="LEFT" width="100%">
    </div>

    <div class="SECT1">
      <h1 class="SECT1"><a name="SECOH">12.16. Single Printcap File
      for Large Installation</a></h1>

      <p>One of the major problems faced by administrators of large
      sites is how to distribute printcap information. They would
      like to have a single printcap file either distributed by a
      file server (NFS) or by some other method such as <tt class=
      "LITERAL">rdist</tt>. By using the <tt class=
      "LITERAL">server</tt> and <tt class="LITERAL">oh</tt> tags,
      information for the specific sites can be separated out. For
      example:</p>

      <div class="INFORMALEXAMPLE">
        <a name="AEN6045"></a>
<pre class="SCREEN">
    # printcap
    pr1:lp=pr1@serverhost1:oh=*.eng.site.com,130.191.12.0/24
    pr2:lp=pr1@serverhost1:oh=*.eng.site.com,130.191.12.0/24
    pr1:lp=pr2@serverhost2:oh=*.admin.site.com
    pr2:lp=pr2@serverhost2:oh=*.admin.site.com
    pr1:server:oh=serverhost1.eng.com:lp=/dev/lp:tc=.common
    pr2:server:oh=serverhost2.admin.com:lp=/dev/lp:tc=.common
    .common:sd=/usr/local/lpd/%P
</pre>
      </div>
      <br>
      <br>

      <p>The above example has some interesting effects. The <tt
      class="LITERAL">pattern</tt> is used as a <i class=
      "EMPHASIS">glob</i> pattern and is applied to the fully
      qualified domain name (FQDN) of the host reading the printcap
      file. For example, <tt class="FILENAME">*.eng.site.com</tt>
      would match host <tt class="FILENAME">h1.eng.site.com</tt>
      but would not match <tt class=
      "FILENAME">h1.admin.site.com</tt>. Thus, the effects of the
      first couple of entries would be to specify that the <tt
      class="LITERAL">pr1</tt> and <tt class="LITERAL">pr2</tt>
      printers on the <tt class="LITERAL">eng</tt> hosts would be
      <tt class="LITERAL">pr1@serverhost1</tt>, and on the <tt
      class="LITERAL">admin</tt> hosts would be <tt class=
      "LITERAL">pr2@serverhost2</tt>,</p>

      <p>Also, the lpd daemons on <tt class=
      "LITERAL">serverhost1</tt> and <tt class=
      "LITERAL">serverhost2</tt> would extract the additional
      information for <tt class="LITERAL">pr1</tt> and <tt class=
      "LITERAL">pr2</tt> respectively, overriding the common <tt
      class="LITERAL">lp</tt> entries.</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=
          "printcappath.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=
          "x6065.htm" accesskey="N">Next</a></td>
        </tr>

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

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

          <td width="33%" align="right" valign="top">Management
          Strategies for Large Installations</td>
        </tr>
      </table>
    </div>
  </body>
</html>