From: Evan Hunt <each@isc.org>
Date: Tue, 25 Sep 2012 23:33:12 +0000 (-0700)
Subject: improve managed-keys-directory documentation
X-Git-Tag: v9.10.0a1~872
X-Git-Url: http://git.ipfire.org/gitweb/?a=commitdiff_plain;h=9e8dbb4276b32c7fe304e7fe256037f408806798;p=thirdparty%2Fbind9.git

improve managed-keys-directory documentation
---

diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml
index fa8f2b74c64..c3eb51aea84 100644
--- a/doc/arm/Bv9ARM-book.xml
+++ b/doc/arm/Bv9ARM-book.xml
@@ -5518,11 +5518,18 @@ badresp:1,adberr:0,findfail:0,valfail:0]
             <term><command>managed-keys-directory</command></term>
             <listitem>
               <para>
-		The directory used to hold the files used to track managed keys.
-		By default it is the working directory.  It there are no
-		views then the file <filename>managed-keys.bind</filename>
-		otherwise a SHA256 hash of the view name is used with
-		<filename>.mkeys</filename> extension added.
+                Specifies the directory in which to store the files that
+                track managed DNSSEC keys.  By default, this is the working
+                directory.
+              </para>
+              <para>
+                If <command>named</command> is not configured to use views,
+                then managed keys for the server will be tracked in a single
+                file called <filename>managed-keys.bind</filename>.
+                Otherwise, managed keys will be tracked in separate files,
+                one file per view; each file name will be the SHA256 hash
+                of the view name, followed by the extension
+                <filename>.mkeys</filename>.
               </para>
             </listitem>
           </varlistentry>