cache size limiting is no longer a 'future' feature; misc other cleanup

doc/arm/Bv9ARM-book.xml

@@ -2,7 +2,7 @@
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.0//EN"
                "http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd">
 
-<!-- File: $Id: Bv9ARM-book.xml,v 1.141 2001/06/18 22:18:53 gson Exp $ -->
+<!-- File: $Id: Bv9ARM-book.xml,v 1.142 2001/06/18 22:34:37 gson Exp $ -->
 
 <book>
 <title>BIND 9 Administrator Reference Manual</title>
@@ -363,8 +363,11 @@ be placed inside a firewall.</para>
 
 </chapter>
 
-  <chapter id="ch02"><title><acronym>BIND</acronym> Resource Requirements</title>
-<sect1><title>Hardware requirements</title>
+<chapter id="ch02"><title><acronym>BIND</acronym> Resource Requirements</title>
+
+<sect1>
+<title>Hardware requirements</title>
+
 <para><acronym>DNS</acronym> hardware requirements have traditionally been quite modest.
 For many installations, servers that have been pensioned off from
 active duty have performed admirably as <acronym>DNS</acronym> servers.</para>
@@ -378,10 +381,11 @@ multiprocessor systems for installations that need it.</para></sect1>
 for serving of static zones without caching, to enterprise-class
 machines if you intend to process many dynamic updates and DNSSEC
 signed zones, serving many thousands of queries per second.</para></sect1>
-<sect1><title>Memory Requirements </title>
+
+<sect1><title>Memory Requirements</title>
 <para>The memory of the server has to be large enough to fit the
-cache and zones loaded off disk. Future releases of <acronym>BIND</acronym> 9 will
-provide methods to limit the amount of memory used by the cache,
+cache and zones loaded off disk.  The <command>max-cache-size</command>
+option can be used to limit the amount of memory used by the cache,
 at the expense of reducing cache hit rates and causing more <acronym>DNS</acronym>
 traffic. It is still good practice to have enough memory to load
 all zone and cache data into memory &mdash; unfortunately, the best way
@@ -390,6 +394,7 @@ in operation. After a few weeks the server process should reach
 a relatively stable size where entries are expiring from the cache as
 fast as they are being inserted. Ideally, the resource limits should
 be set higher than this stable size.</para></sect1>
+
 <sect1><title>Nameserver Intensive Environment Issues</title>
 <para>For nameserver intensive environments, there are two alternative
 configurations that may be used. The first is where clients and
@@ -2237,10 +2242,10 @@ Usage</title>
       that contains the users who should have access.</para>
 
       <para>The UNIX control channel type of <acronym>BIND</acronym> 8 is not supported
-      in <acronym>BIND</acronym> 9.0.0, and is not expected to be added in future
+      in <acronym>BIND</acronym> 9, and is not expected to be added in future
       releases.  If it is present in the controls statement from a
-      <acronym>BIND</acronym> 8 configuration file, a non-fatal warning will be
-      logged.</para>
+      <acronym>BIND</acronym> 8 configuration file, it is ignored
+      and a warning is logged.</para>
 
     </sect2>
     <sect2>
@@ -2248,8 +2253,7 @@ Usage</title>
       <programlisting>include <replaceable>filename</replaceable>;</programlisting>
     </sect2>
     <sect2>
-      <title><command>include</command> Statement Definition and
-Usage</title>
+      <title><command>include</command> Statement Definition and Usage</title>
 
       <para>The <command>include</command> statement inserts the
       specified file at the point that the <command>include</command>
@@ -2262,7 +2266,7 @@ Usage</title>
     </sect2>
     <sect2>
       <title><command>key</command> Statement Grammar</title>
-      <programlisting>key <replaceable>key_id</replaceable> {
+<programlisting>key <replaceable>key_id</replaceable> {
     algorithm <replaceable>string</replaceable>;
     secret <replaceable>string</replaceable>;
 };
@@ -2991,7 +2995,7 @@ The default is <userinput>no</userinput>.
 <varlistentry><term><command>multiple-cnames</command></term>
 <listitem><para>This option was used in <acronym>BIND</acronym> 8 to allow
 a domain name to allow multiple CNAME records in violation of the
-DNS standards.  <acronym>BIND</acronym> 9.1 always strictly
+DNS standards.  <acronym>BIND</acronym> 9.2 always strictly
 enforces the CNAME rules both in master files and dynamic updates.
 </para></listitem></varlistentry>
 

doc/arm/Bv9ARM.ch02.html

@@ -164,11 +164,11 @@ NAME="AEN235"
 ></H1
 ><P
 >The memory of the server has to be large enough to fit the
-cache and zones loaded off disk. Future releases of <SPAN
-CLASS="acronym"
->BIND</SPAN
-> 9 will
-provide methods to limit the amount of memory used by the cache,
+cache and zones loaded off disk.  The <B
+CLASS="command"
+>max-cache-size</B
+>
+option can be used to limit the amount of memory used by the cache,
 at the expense of reducing cache hit rates and causing more <SPAN
 CLASS="acronym"
 >DNS</SPAN

doc/arm/Bv9ARM.ch06.html

@@ -1658,13 +1658,13 @@ CLASS="acronym"
       in <SPAN
 CLASS="acronym"
 >BIND</SPAN
-> 9.0.0, and is not expected to be added in future
+> 9, and is not expected to be added in future
       releases.  If it is present in the controls statement from a
       <SPAN
 CLASS="acronym"
 >BIND</SPAN
-> 8 configuration file, a non-fatal warning will be
-      logged.</P
+> 8 configuration file, it is ignored
+      and a warning is logged.</P
 ></DIV
 ><DIV
 CLASS="sect2"
@@ -1695,8 +1695,7 @@ NAME="AEN1509"
 >6.2.6. <B
 CLASS="command"
 >include</B
-> Statement Definition and
-Usage</A
+> Statement Definition and Usage</A
 ></H2
 ><P
 >The <B
@@ -4560,7 +4559,7 @@ a domain name to allow multiple CNAME records in violation of the
 DNS standards.  <SPAN
 CLASS="acronym"
 >BIND</SPAN
-> 9.1 always strictly
+> 9.2 always strictly
 enforces the CNAME rules both in master files and dynamic updates.
 </P
 ></DD

doc/arm/Bv9ARM.html

@@ -459,8 +459,7 @@ HREF="Bv9ARM.ch06.html#AEN1509"
 ><B
 CLASS="command"
 >include</B
-> Statement Definition and
-Usage</A
+> Statement Definition and Usage</A
 ></DT
 ><DT
 >6.2.7. <A