From owner-freebsd-current@FreeBSD.ORG Tue Sep 28 09:55:59 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 907BD16A4CE for ; Tue, 28 Sep 2004 09:55:59 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77C0D43D5A for ; Tue, 28 Sep 2004 09:55:59 +0000 (GMT) (envelope-from DougB@freebsd.org) Received: from lap (c-24-130-110-32.we.client2.attbi.com[24.130.110.32]) by comcast.net (rwcrmhc11) with SMTP id <2004092809555801300lltq4e>; Tue, 28 Sep 2004 09:55:59 +0000 Date: Tue, 28 Sep 2004 02:55:58 -0700 (PDT) From: Doug Barton To: Juha Saarinen In-Reply-To: Message-ID: <20040928024928.R5094@ync.qbhto.arg> References: <1096042856.24267.6.camel@purgatory.ceribus.net> <20040924222550.F6548@URF.trarfvf> <20040925001835.U7126@URF.trarfvf><20040927184543.I911@bo.vpnaa.bet> 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 09:55:59 -0000 On Tue, 28 Sep 2004, Juha Saarinen wrote: > On Mon, 27 Sep 2004 18:54:01 -0700 (PDT), Doug Barton wrote: >> 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. > > Humm, that does seem like the right way to do it, instead of working > around the issue by changing the PID file location in two different > places. Thanks. >> 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. > > True -- however, this is likely to bite people who migrate from other > platforms where you don't have to specify the PID file location in > named.conf, unless you want it in a non-default location. But, people > have plenty of toes I suppose... :-) *nod* Now that I've committed the chroot defaults, I may consider changing this back to /var/run/named.pid .... I'll wait to see how the chroot stuff falls out for people. >> 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? > > Well, rndc is the vendor-supplied tool for controlling the operation of named. I think you missed the part of my previous message where I talked about how the current system offers the maximum in terms of features and flexibility. > The man page for named(8) says: > > "In routine operation, signals should not be used to control the name- > server; rndc should be used instead." That same man page then defines the behavior for SIGINT and SIGTERM. Killing named with a signal in this case is harmless, and should be functionally equivalent to 'rndc stop', except in those cases where rndc is buggered for some reason. > Incidentally, shouldn't the 'rcvar" command print out all the options > used in rc.conf for running named? You might want to follow up with this question on freebsd-rc@freebsd.org. Hope this helps, Doug -- This .signature sanitized for your protection