[deployment-guide/comm-rel: 362/727] Updated the `logging' statement description.

[Jaromir Hradilek]

commit 7690f16f2650b8e618572ee718fb46326a2f87df
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Fri Aug 13 15:02:03 2010 +0200

    Updated the `logging' statement description.

 en-US/The_BIND_DNS_Server.xml |    7 ++-----
 1 files changed, 2 insertions(+), 5 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index 2fae14d..2f918bf 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -855,14 +855,11 @@ options {
           <term><command>logging</command></term>
           <listitem>
             <para>
-              Allows for the use of multiple types of logs, called <firstterm>channels</firstterm>. By using the <command>channel</command> option within the <command>logging</command> statement, a customized type of log can be constructed — with its own file name (<command>file</command>), size limit (<command>size</command>), versioning (<command>version</command>), and level of importance (<command>severity</command>). Once a customized channel <!-- RHEL5:  has been  -->is defined, a <command>category</command> option is used to categorize the channel and begin logging when <command>named</command> is restarted.
+              The <command>logging</command> statement allows you to use multiple types of logs, or so called <firstterm>channels</firstterm>. By using the <option>channel</option> option within the statement, you can construct a customized type of log with its own file name (<option>file</option>), size limit (<option>size</option>), versioning (<option>version</option>), and level of importance (<option>severity</option>). Once a customized channel is defined, a <option>category</option> option is used to categorize the channel and begin logging when the <systemitem class="service">named</systemitem> service is restarted.
             </para>
             <para>
-              By default, <command>named</command> logs standard messages to the <command>rsyslog</command> daemon, which places them in <filename>/var/log/messages</filename>. This occurs because several standard channels are built into BIND with various severity levels, such as <command>default_syslog</command> (which handles informational logging messages) and <command>default_debug</command> (which specifically handles debugging messages). A default category, called <command>default</command>, uses the built-in channels to do normal logging without any special configuration.
+              By default, <systemitem class="service">named</systemitem> sends standard messages to the <systemitem class="service">rsyslog</systemitem> daemon, which places them in <filename>/var/log/messages</filename>. Several standard channels are built into BIND with various severity levels, such as <literal>default_syslog</literal> (which handles informational logging messages) and <literal>default_debug</literal> (which specifically handles debugging messages). A default category, called <literal>default</literal>, uses the built-in channels to do normal logging without any special configuration.
             </para>
-            <!-- RHEL5:  ddomingo at redhat.com: above <para>replaces following:
-          <para>By default, <command>named</command> logs standard messages to the <command>syslog</command> daemon, which places them in <filename>/var/log/messages</filename>. This occurs because several standard channels are built into BIND with various severity levels, such as one that handles informational logging messages (<command>default_syslog</command>) and another that specifically handles debugging messages (<command>default_debug</command>). A default category, called <command>default</command>, uses the built-in channels to do normal logging without any special configuration.</para>
- -->
             <para>
               Customizing the logging process can be a very detailed process and is beyond the scope of this chapter. For information on creating custom BIND logs, refer to the <citetitle>BIND 9 Administrator Reference Manual</citetitle> referenced in <xref linkend="s2-bind-installed-docs"/>.
             </para>