From owner-freebsd-current@FreeBSD.ORG Sat Sep 25 00:06:13 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 B2E8116A4CE; Sat, 25 Sep 2004 00:06:13 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9156043D48; Sat, 25 Sep 2004 00:06:13 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 46FE7F1A1E; Fri, 24 Sep 2004 17:06:11 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01574-02; Fri, 24 Sep 2004 17:06:10 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id B3D38F196D; Fri, 24 Sep 2004 17:06:10 -0700 (PDT) From: Sean McNeil To: Doug Barton In-Reply-To: <20040925001835.U7126@URF.trarfvf> References: <1096042856.24267.6.camel@purgatory.ceribus.net> <20040924222550.F6548@URF.trarfvf> <1096064849.1047.7.camel@server.mcneil.com> <20040925001835.U7126@URF.trarfvf> Content-Type: text/plain Message-Id: <1096070770.2712.6.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 24 Sep 2004 17:06:10 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: Dag-Erling =?ISO-8859-1?Q?Sm=F8rgrav?= 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: Sat, 25 Sep 2004 00:06:13 -0000 On Fri, 2004-09-24 at 16:44, Doug Barton wrote: > On Fri, 24 Sep 2004, Sean McNeil wrote: > > DES made an honest mistake in rc.conf. I was waiting for him to back it > out himself, but apparently he's off having a life or something. :) I > went ahead and fixed it a bit ago. I see that has gone in. Thanks! > You mentioned "some files," do you know of anywhere else that it is not > correct? This is white noise. Sorry. I thought that the intention was to move it to /var/run/named.conf so I changed my /etc/named/named.conf. I put it back when I realized that the pid file had to be in a directory owned by bind. > > Also, the /etc/rc.d/named script will do an > > > > ln -fs "${named_chrootdir}${pidfile}" ${pidfile} > > > > if named_symlink_enable is set (which is by default). Please protect > > this with > > > > if [ -n "$named_chrootdir" ]; then > > On my system this fails harmlessly, but you're right, it shouldn't be > run if there is no chroot. I'll commit a fix for this in a second. I appreciate it. It probably would fail harmlessly for me too after I figured out what was going on. > > for those who do not have a chrootdir. Otherwise we end up with a > > recursive link. > > Actually the final result of this situation depends on the configuration > options. But you're right, this bullet should be removed from the > foot-shooting gun. > > >> 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. > > > > This is broken too. If named_chrootdir isn't set, then confgen_chroot > > doesn't get set and it messes up the invokation of rndc-confgen. I > > think taking the "" off of the ${confgen_chroot} will solve this but I'm > > not sure. > > Only broken for the non-chroot case. :) You're right about the fix > though, I committed the wrong version when I was testing it last night. > Thanks for the bug report. My pleasure. Glad to help any little way I can to make FreeBSD what it is. Sean