From owner-freebsd-current@FreeBSD.ORG Tue Sep 28 01:54:07 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 B704316A4CE for ; Tue, 28 Sep 2004 01:54:07 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3255E43D46 for ; Tue, 28 Sep 2004 01:54:07 +0000 (GMT) (envelope-from DougB@freebsd.org) Received: from ob.icann.org ([192.0.35.106]) by comcast.net (sccrmhc11) with SMTP id <20040928015405011005q6ace> (Authid: domain_name_tsar); Tue, 28 Sep 2004 01:54:06 +0000 Date: Mon, 27 Sep 2004 18:54:01 -0700 (PDT) From: Doug Barton To: Juha Saarinen In-Reply-To: Message-ID: <20040927184543.I911@bo.vpnaa.bet> References: <1096042856.24267.6.camel@purgatory.ceribus.net> <20040924222550.F6548@URF.trarfvf> <20040925001835.U7126@URF.trarfvf> Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= cc: freebsd-current@freebsd.org 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: Tue, 28 Sep 2004 01:54:07 -0000 On Tue, 28 Sep 2004, Juha Saarinen wrote: > The PID file location for currently hardcoded to /var/run in the named binary. You are correct. > Is there a good reason for not changing that to /var/run/named/pid as > the default on FreeBSD, instead of adjusting the location in both > /etc/defaults/rc.conf and named.conf? A couple of them actually. We do not want to edit the files as they come from the vendor without a really good reason, and this isn't one. I have a long term plan to write some patches to turn the pid file path into a --configure defineable variable and send it to the ISC folks, but it's frankly not that high a priority. > This is error-prone, and easy to forget -- if you do, it means named > won't start up as it cannot write the PID file to the default > location. If you use the system as installed, and/or start from the default files, it's all there for you. If you choose to vary from that path, it's pretty much up to you to know what you're doing and why. There are only so many bullets you can take out of the foot-shooting gun. That said, I did add a comment to the src/etc/default/rc.conf file which indicates that if you change the pid file name there, you should change it in named.conf as well to make it easier for users to do the right thing. Finally, the way named fails in this case (totally) is actually the safest way to handle it. No user can accidentally start named with the wrong configuration and have it running in a manner other than what they expect. This is a much more serious problem, and would be worthy of a better solutino if it existed. The problem you describe here is a learning curve issue, and BIND has a lot of those. > Second, shouldn't /etc/rc.d/named be rewritten to take rndc into > account, and not use /etc/rc.subr? What would your goal be? With the current behavior, '/etc/rc.d/named stop' can recover from situations where 'rndc stop' fails. Why would you want to take that functionality away? Doug -- This .signature sanitized for your protection