On Fri, 24 Sep 2004, Dag-Erling Smørgrav wrote: > Grover Lines <grover_at_ceribus.net> writes: >> named_pidfile="/var/run/named/pid" # Must set this in named.conf as well > ^^^^^^^^^^^^^^^^^^ > should be /var/run/named.pid, fixed in CVS. > > DES > It's actually not named.pid in our structure. As explained in the note behind the variable, we set the pid-file variable in named.conf so that named running wit h -u bind (but not chrooted) will still be able to drop a pid file in /var/run/named, which is chowned to user bind. To answer Grover's question, it really depends on what you want to use it for. The system named.conf will run fine for bind 9 as a resolver, now that the /etc/rc.d/named script has been updated to create an rndc.key file if one doesn't exist. If all you want to do is start up named as a resolver, named_enable="yes" is all you need. You don't need to specify the conf file to run the system's version of bind, that path is defined in. I'm currently working on a setup so that named can be started chrooted by default. Not sure if that will get in before 5.3-RELEASE or not, but I'm hoping it will. Doug -- This .signature sanitized for your protectionReceived on Fri Sep 24 2004 - 19:28:11 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:13 UTC