From owner-freebsd-current@FreeBSD.ORG Fri Sep 24 21:28:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F9C016A4CE for ; Fri, 24 Sep 2004 21:28:11 +0000 (GMT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B51643D2D for ; Fri, 24 Sep 2004 21:28:11 +0000 (GMT) (envelope-from DougB@freebsd.org) Received: from [192.168.9.149] (unknown[195.172.110.163]) by comcast.net (rwcrmhc12) with ESMTP id <2004092421280901400k9s1ne> (Authid: domain_name_tsar); Fri, 24 Sep 2004 21:28:10 +0000 Date: Fri, 24 Sep 2004 22:27:49 +0100 (BST) From: Doug Barton To: =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= In-Reply-To: Message-ID: <20040924222550.F6548@URF.trarfvf> References: <1096042856.24267.6.camel@purgatory.ceribus.net> Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-608998099-1096061269=:6548" cc: freebsd-current@freebsd.org cc: Grover Lines Subject: Re: Proper way to run bind9 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2004 21:28:11 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-608998099-1096061269=:6548 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8BIT On Fri, 24 Sep 2004, Dag-Erling Smørgrav wrote: > Grover Lines 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 protection --0-608998099-1096061269=:6548--