From: Mark Andrews <marka@isc.org>
Date: Thu, 31 May 2007 22:33:12 +0000 (+0000)
Subject: update from jeremy
X-Git-Tag: v9.2.0b1^2~26
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bca86b6c1c1e28ee0447db2c6f12c110d72b7098;p=thirdparty%2Fbind9.git

update from jeremy
---

diff --git a/bin/rndc/rndc.docbook b/bin/rndc/rndc.docbook
index 5d63f64b39e..77d2f2666ae 100644
--- a/bin/rndc/rndc.docbook
+++ b/bin/rndc/rndc.docbook
@@ -18,7 +18,7 @@
  - PERFORMANCE OF THIS SOFTWARE.
 -->
 
-<!-- $Id: rndc.docbook,v 1.7.2.7 2007/05/09 02:11:44 marka Exp $ -->
+<!-- $Id: rndc.docbook,v 1.7.2.8 2007/05/31 22:33:12 marka Exp $ -->
 
 <refentry>
   <refentryinfo>
@@ -78,7 +78,7 @@
         <command>rndc</command> communicates with the name server
 	over a TCP connection, sending commands authenticated with
 	digital signatures.  In the current versions of
-	<command>rndc</command> and <command>named</command> named
+      <command>rndc</command> and <command>named</command>,
         the only supported authentication algorithm is HMAC-MD5,
 	which uses a shared secret on each end of the connection.
 	This provides TSIG-style authentication for the command
@@ -158,15 +158,15 @@
       </varlistentry>
 
       <varlistentry>
-        <term>-y <replaceable class="parameter">keyid</replaceable></term>
+        <term>-y <replaceable class="parameter">key_id</replaceable></term>
 	<listitem>
 	  <para>
-	       Use the key <replaceable class="parameter">keyid</replaceable>
+	       Use the key <replaceable class="parameter">key_id</replaceable>
 	       from the configuration file.
-	       <replaceable class="parameter">keyid</replaceable> must be
+	       <replaceable class="parameter">key_id</replaceable> must be
 	       known by named with the same algorithm and secret string
 	       in order for control message validation to succeed.
-	       If no <replaceable class="parameter">keyid</replaceable>
+	       If no <replaceable class="parameter">key_id</replaceable>
 	       is specified, <command>rndc</command> will first look
 	       for a key clause in the server statement of the server
 	       being used, or if no server statement is present for that