improve managed-keys-directory documentation

This commit is contained in:
Evan Hunt 2012-09-25 16:33:12 -07:00
parent 14b92348e7
commit 2b58833f58

View file

@ -5496,11 +5496,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>