[deployment-guide/comm-rel: 345/727] Improved the formatting of the sample named.conf.

Jaromir Hradilek jhradile at fedoraproject.org
Tue Oct 19 12:53:40 UTC 2010


commit 126d91c9e6b617e61dd50133891d01924a9f6cf4
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Thu Aug 12 12:28:33 2010 +0200

    Improved the formatting of the sample named.conf.

 en-US/The_BIND_DNS_Server.xml |   24 ++++++++++++------------
 1 files changed, 12 insertions(+), 12 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index c658d34..ca0d05c 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -283,20 +283,20 @@
     <para>
       The configuration file consists of a collection of statements with nested options surrounded by opening and closing curly brackets (that is, <literal>{</literal> and <literal>}</literal>). Note that when editing the file, you have to be careful not to make any syntax error, otherwise the <systemitem class="service">named</systemitem> service will not start. A typical <filename>/etc/named.conf</filename> file is organized as follows:
     </para>
-    <screen><replaceable>&lt;statement-1&gt;</replaceable> ["<replaceable>&lt;statement-1-name&gt;</replaceable>"] [<replaceable>&lt;statement-1-class&gt;</replaceable>] {
-  <replaceable>&lt;option-1&gt;</replaceable>;
-  <replaceable>&lt;option-2&gt;</replaceable>;
-  <replaceable>&lt;option-N&gt;</replaceable>;
+    <screen><replaceable>statement-1</replaceable> ["<replaceable>statement-1-name</replaceable>"] [<replaceable>statement-1-class</replaceable>] {
+  <replaceable>option-1</replaceable>;
+  <replaceable>option-2</replaceable>;
+  <replaceable>option-N</replaceable>;
 };
-<replaceable>&lt;statement-2&gt;</replaceable> ["<replaceable>&lt;statement-2-name&gt;</replaceable>"] [<replaceable>&lt;statement-2-class&gt;</replaceable>] {
-  <replaceable>&lt;option-1&gt;</replaceable>;
-  <replaceable>&lt;option-2&gt;</replaceable>;
-  <replaceable>&lt;option-N&gt;</replaceable>;
+<replaceable>statement-2</replaceable> ["<replaceable>statement-2-name</replaceable>"] [<replaceable>statement-2-class</replaceable>] {
+  <replaceable>option-1</replaceable>;
+  <replaceable>option-2</replaceable>;
+  <replaceable>option-N</replaceable>;
 };
-<replaceable>&lt;statement-N&gt;</replaceable> ["<replaceable>&lt;statement-N-name&gt;</replaceable>"] [<replaceable>&lt;statement-N-class&gt;</replaceable>] {
-  <replaceable>&lt;option-1&gt;</replaceable>;
-  <replaceable>&lt;option-2&gt;</replaceable>;
-  <replaceable>&lt;option-N&gt;</replaceable>;
+<replaceable>statement-N</replaceable> ["<replaceable>statement-N-name</replaceable>"] [<replaceable>statement-N-class</replaceable>] {
+  <replaceable>option-1</replaceable>;
+  <replaceable>option-2</replaceable>;
+  <replaceable>option-N</replaceable>;
 };</screen>
     <note>
       <title>Note: Running BIND in a Chroot Environment</title>


More information about the docs-commits mailing list