Location of files is different between 9.1 and 9.2

[George Young]

There is something different with the way 9.2.0 is handling the location of
the files. When I installed it on  RH7.2 on top of 9.1.3 system, the
/configure routines put the files in different places then the 9.1.3
/configure routines. I had to specify more  /configure options to get the
files into the same directories as the previous installs.

For example the 9.1 install used
 ./configure --prefix=/usr

The 9.2.0 needed
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var

I would think that each release of bind would have the files defaulting into
the same directories as the previous releases.

Is there a consensus of opinion on where these files should be anyway on a
Linux system?


George Young / G-L Data, Inc / Morristown, NJ



<-----Original Message-----
<From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
<Behalf Of Jari Takkala
<Sent: Thursday, December 06, 2001 8:33 PM
<To: bind-users at isc.org
<Subject: Why does BIND create a new pid file on conf. reload?
<
<
<
<
<Hello,
<
<It seems that if I use ndc to reload the configuration for
<named, BIND will
<try and update the pid file, even though the PID of named does
<not change.
<
<Whereas, if I do 'ndc restart -u bind -g bind', named will
<restart and create
<the pid file as root, chown()'ing it to the user id and group
<id specified on
<the command line, before setuid()'ing to user bind.
<
<Why does named bother to attempt to create a new pid file if
<its own PID does
<not change (ie. if executing 'ndc reload')? If I am running
<named as another
<user, such as 'bind', then it will fail to create the new PID
<file as named
<does not have permission to unlink /var/run/named.pid. This results in
<entries such as the following in my log files:
<
<Dec  6 19:12:48 lithium named[232]: couldn't create pid file'
</var/run/named.pid'
<
<Does anyone else think that this is a bug, or am I missing something?
<
<Here are my configuration details:
<named version 8.2.4-REL, run as 'named -u bind -g bind'
<
<> ls -ld /var/run
<drwxr-xr-x  3 root  wheel  512 Dec  6 20:22 /var/run
<
<> ls -l /var/run/named.pid
<-rw-r--r--  1 bind  bind  5 Dec  6 19:22 /var/run/named.pid
<
<Regards,
<
<Jari Takkala
<
<--
<Jari Takkala
<Senior UNIX Administrator and Network Engineer
<tel: +1 416-894-8649
<fax: +1 416-222-7748
<email: jari at infid.net
<
<