Repository :
http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
---------------------------------------------------------------
commit e7db71e09bfa00401c3735e93dea0ab5beb7d93c
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Wed Aug 20 22:52:35 2014 +0200
Improve: BIND in chroot environment
---------------------------------------------------------------
en-US/BIND.xml | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/en-US/BIND.xml b/en-US/BIND.xml
index 8c0a08a..d324577 100644
--- a/en-US/BIND.xml
+++ b/en-US/BIND.xml
@@ -99,8 +99,8 @@
<note>
<title>Running BIND in a chroot environment</title>
<para>
- If you have installed the <package>bind-chroot</package> package, the
BIND service will run in the <filename
class="directory">/var/named/chroot</filename> environment. In that
case, the initialization script will mount the above configuration files using the
<command>mount --bind</command> command, so that you can manage the
configuration outside this environment. There is no need to copy anything into the
<filename class="directory">/var/named/chroot</filename> directory
because it is mounted automatically. This simplifies maintenance since you do not need to
take any special care of <systemitem
class="service">BIND</systemitem> configuration files if it is run in a
<filename class="directory">chroot</filename> environment. You can
organize everything as you would with <systemitem
class="service">BIND</systemitem> not running in a
<filename>chroot</filename> environment.</para>
- <para>The following directories are automatically mounted into <filename
class="directory">/var/named/chroot</filename> if they are empty in the
<filename class="directory">/var/named/chroot</filename> directory.
They must be kept empty if you want them to be mounted into <filename
class="directory">/var/named/chroot</filename>:
+ If you have installed the <package>bind-chroot</package> package, the
BIND service will run in the <command>chroot</command> environment. In that
case, the initialization script will mount the above configuration files using the
<command>mount --bind</command> command, so that you can manage the
configuration outside this environment. There is no need to copy anything into the
<filename class="directory">/var/named/chroot/</filename> directory
because it is mounted automatically. This simplifies maintenance since you do not need to
take any special care of <systemitem
class="service">BIND</systemitem> configuration files if it is run in a
<command>chroot</command> environment. You can organize everything as you
would with <systemitem class="service">BIND</systemitem> not running
in a <command>chroot</command> environment.</para>
+ <para>The following directories are automatically mounted into <filename
class="directory">/var/named/chroot/</filename> if they are empty in
the <filename class="directory">/var/named/chroot/</filename>
directory. They must be kept empty if you want them to be mounted into <filename
class="directory">/var/named/chroot/</filename>:
<itemizedlist>
<listitem>
<para>
@@ -131,7 +131,7 @@
</para>
<para>
- The following files are also mounted if the target file does not exist in
<filename class="directory">/var/named/chroot</filename>.
+ The following files are also mounted if the target file does not exist in
<filename class="directory">/var/named/chroot/</filename>:
<itemizedlist>
<listitem>
<para>
@@ -182,7 +182,7 @@
<section id="sec-Installing_Bind_In_A_Chroot_Environment">
<title>Installing BIND in a chroot Environment</title>
<para>
-To install <application>BIND</application> to run in a chroot environment,
issue the following command as <systemitem
class="username">root</systemitem>:
+To install <application>BIND</application> to run in a
<command>chroot</command> environment, issue the following command as
<systemitem class="username">root</systemitem>:
<screen>~]# <command>yum install
bind-chroot</command></screen>
</para>
<para>
@@ -198,7 +198,7 @@ Then, to enable the <systemitem
class="daemon">named-chroot</systemitem> service
<screen>~]# <command>systemctl start
named-chroot</command></screen>
</para>
<para>
- To check the status of the named-chroot service, issue the following command as
<systemitem class="username">root</systemitem>:
+ To check the status of the <systemitem
class="daemon">named-chroot</systemitem> service, issue the following
command as <systemitem class="username">root</systemitem>:
<screen>~]# <command>systemctl status
named-chroot</command></screen>
</para>
</section>