From owner-freebsd-arch@FreeBSD.ORG Wed Sep 21 14:09:45 2005 Return-Path: X-Original-To: arch@FreeBSD.ORG Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19A0C16A41F; Wed, 21 Sep 2005 14:09:45 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABD5243D45; Wed, 21 Sep 2005 14:09:44 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j8LE9hDe007444; Wed, 21 Sep 2005 07:09:43 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j8LE9h1I007443; Wed, 21 Sep 2005 07:09:43 -0700 Date: Wed, 21 Sep 2005 07:09:43 -0700 From: Brooks Davis To: "Matthew N. Dodd" Message-ID: <20050921140943.GB3739@odin.ac.hmc.edu> References: <20050826202713.X1915@sasami.jurai.net> <20050827014153.GA14720@odin.ac.hmc.edu> <20050826221016.B1915@sasami.jurai.net> <20050827170600.GB14720@odin.ac.hmc.edu> <20050828022351.F63789@sasami.jurai.net> <20050908181052.GH31354@odin.ac.hmc.edu> <20050914091957.P56212@sasami.jurai.net> <43293189.5000200@FreeBSD.org> <20050915094948.K79434@sasami.jurai.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pvezYHf7grwyp3Bc" Content-Disposition: inline In-Reply-To: <20050915094948.K79434@sasami.jurai.net> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: arch@FreeBSD.ORG, Doug Barton Subject: Re: [CFR] reflect resolv.conf update to running application X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2005 14:09:45 -0000 --pvezYHf7grwyp3Bc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 15, 2005 at 09:59:48AM -0400, Matthew N. Dodd wrote: > On Thu, 15 Sep 2005, Doug Barton wrote: > >Yes, include works, but it runs a similar risk to modifying the=20 > >named.conf file, namely if the syntax of the the statements in the=20 > >include file are not right, loading named.conf will fail. So, we should= =20 > >build some caution into the process of updating the file, but that's=20 > >easily done with the named-checkconf program that comes with the=20 > >distribution. >=20 > I'm not sure such paranoia is needed; dhclient has always exposed the=20 > system to the risk of having an invalid resolv.conf and regenerating the= =20 > named.conf file is no different. Since we're regenerating the included= =20 > file completely I don't see that this is risky at all. The domain name server values will be valid host names. dhclient checks that so we can count on it. I had broken the search checks, but have since fixed that. It might be useful to still write a resolv.conf that only refers to 127.0.0.1 and includes the search directive if we write the forwarder's file. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --pvezYHf7grwyp3Bc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDMWmlXY6L6fI4GtQRAqNYAJ4z8cXGL57onEUlzreEzOUHH7md0QCfaUK0 KQz7m2YCNoK/iQhHAEzbW9M= =YJjj -----END PGP SIGNATURE----- --pvezYHf7grwyp3Bc--