From owner-freebsd-current@FreeBSD.ORG Sat Oct 2 09:59:33 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 EF1EF16A4CE; Sat, 2 Oct 2004 09:59:33 +0000 (GMT) Received: from smtp2.jazztel.es (smtp2.jazztel.es [62.14.3.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A51643D58; Sat, 2 Oct 2004 09:59:32 +0000 (GMT) (envelope-from josemi@freebsd.jazztel.es) Received: from antivirus by smtp2.jazztel.es with antivirus id 1CDgfn-000322-00 Sat, 02 Oct 2004 11:59:27 +0200 Received: from [212.106.236.104] (helo=rguez.homeunix.net) by smtp2.jazztel.es with esmtp id 1CDgfm-00031I-00 Sat, 02 Oct 2004 11:59:26 +0200 Received: from orion.redesjm.local (orion.redesjm.local [192.168.254.16]) by rguez.homeunix.net (8.13.1/8.13.1) with ESMTP id i929dpnI002758; Sat, 2 Oct 2004 11:39:52 +0200 (CEST) (envelope-from freebsd@redesjm.local) From: Jose M Rodriguez To: freebsd-current@freebsd.org Date: Sat, 2 Oct 2004 11:39:49 +0200 User-Agent: KMail/1.7 References: <200410021033.37844.freebsd@redesjm.local> <20041002084741.GA55948@ip.net.ua> In-Reply-To: <20041002084741.GA55948@ip.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200410021139.49551.freebsd@redesjm.local> X-AntiVirus: checked by AntiVir Milter 1.1-beta; AVE 6.27.0.12; VDF 6.27.0.81 (host: antares.redesjm.local) X-Virus-Scanned: by antivirus cc: Jose M Rodriguez cc: current@freebsd.org Subject: Re: problems with latest bind9 setup changes 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, 02 Oct 2004 09:59:34 -0000 El S=E1bado, 2 de Octubre de 2004 10:47, Ruslan Ermilov escribi=F3: > Hi Jose, > > On Sat, Oct 02, 2004 at 10:33:37AM +0200, Jose M Rodriguez wrote: > > I'm running named in a sandwitch config form: > > named_flags=3D"-u bind -c /var/named/named.conf > > > > After my last update, I've got my /var/named/ dir polluted by a chroot > > setup. I think this is not the way. > > > > /etc/rc.d/named must do this from chroot_autoupdate() only when required > > to do so. > > > > If /var/named must became a system directory, I can move my config > > to /var/namebd or so. But I like to read HEADS UP about those things. > > There was a HEADS up message sent to the current@ mailing list. > There is also a relevant entry in src/UPDATING, "20040928". > > Ah, so you must /usr/src/UPDATING =2D If enabled, the default is now to run named in a chroot + The default is now to run named in a chroot Using /etc/mtree/BIND.chroot.dist from chroot_autoupdate() is not the same= =20 that put /var/named in /etc/mtree/BSD.var.dist. Well, moving config to var/namedb. IMHO, this is not a good design. If you ask ten admin about the best named= =20 chrooted setup, you'll get, at last, twelve setups. Making strong support for a chrooted named is really needed. But moving th= e=20 release default setup to a strong model on that not. I'll prefer a sandwid= ch=20 setup (named_flags=3D"-u bind", named_chroot=3D"") as release default. > Cheers, Thanks for your time, =2D- josemi