From: Tinderbox User Date: Tue, 10 May 2016 01:05:28 +0000 (+0000) Subject: regen master X-Git-Tag: v9.11.0a2~28 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=56bd026e6c96482dccab83778bf8f9c92c36bf11;p=thirdparty%2Fbind9.git regen master --- diff --git a/doc/arm/Bv9ARM.ch07.html b/doc/arm/Bv9ARM.ch07.html index d234e672749..7dff22023a5 100644 --- a/doc/arm/Bv9ARM.ch07.html +++ b/doc/arm/Bv9ARM.ch07.html @@ -273,16 +273,15 @@ allow-query { !{ !10/8; any; }; key example; }; The chroot Environment

In order for a chroot environment - to - work properly in a particular directory - (for example, /var/named), - you will need to set up an environment that includes everything - BIND needs to run. - From BIND's point of view, /var/named is - the root of the filesystem. You will need to adjust the values of - options like - like directory and pid-file to account - for this. + to work properly in a particular directory (for example, + /var/named), you will need to set + up an environment that includes everything + BIND needs to run. From + BIND's point of view, + /var/named is the root of the + filesystem. You will need to adjust the values of + options like directory and + pid-file to account for this.

Unlike with earlier versions of BIND, you typically will