Re: bind-9 changeover committed.

[Brad Harvell <dfbrad@xxxxxxxxxxx>]

/etc/rc.d/named stop can't find the pid with chroot enabled;
how about this for a patch:

RCS file: /home/dcvs/src/etc/rc.d/named,v
retrieving revision 1.4
diff -u -r1.4 named
--- src/etc/rc.d/named  27 May 2004 18:15:40 -0000      1.4
+++ src/etc/rc.d/named  30 May 2004 01:33:28 -0000
@@ -38,6 +38,6 @@
 # The following variable requires that rc.conf be loaded first
 #
 required_dirs="$named_chrootdir"       # if it is set, it must exist
-pidfile="${named_pidfile:-/var/run/${name}.pid}"
+pidfile="${named_chrootdir}${named_pidfile:-/var/run/${name}.pid}"

 run_rc_command "$1"


as far as named.restart, would it make sense to have it exec
/etc/rc.d/named restart as opposed to having duplicated code?

-Brad


Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx> wrote:
>    * If enabled, named runs in a chrooted environment and as user 'bind'
>      by default now.  Permissions and ownerhip of /etc/namedb and 
>      subdirectories is thus very important.  e.g. /etc/namedb should
>      be owned by root and /etc/namedb/s should be owned by user 'bind'.
>      Most other sub directories in /etc/namedb will be owned by root,
>      except /etc/namedb/var/run which is owned by 'bind'.
> 
>    * named.restart is currently broken (I could use some help there).