From owner-freebsd-arch@FreeBSD.ORG Mon Sep 5 17:17:19 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 57BCC16A41F; Mon, 5 Sep 2005 17:17:19 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B16443D55; Mon, 5 Sep 2005 17:17:15 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:WZ8WavLTGcLvym5mNR/+KaRoH+wCqac5NKcnfUbqXYLyVKmsEMlBrv16vV6hsA/Q@kasuga.mahoroba.org [IPv6:3ffe:501:185b:8010:20b:97ff:fe2e:b521]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.4/8.13.4) with ESMTP/inet6 id j85HH4GR095123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Sep 2005 02:17:05 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Tue, 06 Sep 2005 02:17:04 +0900 Message-ID: From: Hajimu UMEMOTO To: "Matthew N. Dodd" In-Reply-To: <20050826202713.X1915@sasami.jurai.net> References: <20050826202713.X1915@sasami.jurai.net> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/22.0.50 (i386-unknown-freebsd6.0) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.0-BETA4 X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0 (ameno.mahoroba.org [IPv6:3ffe:501:185b:8010::1]); Tue, 06 Sep 2005 02:17:05 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on ameno.mahoroba.org Cc: arch@FreeBSD.ORG 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: Mon, 05 Sep 2005 17:17:19 -0000 Hi, >>>>> On Fri, 26 Aug 2005 20:29:39 -0400 (EDT) >>>>> "Matthew N. Dodd" said: mdodd> On Sat, 20 Aug 2005, Hajimu UMEMOTO wrote: > Our resolver reads resolv.conf once, and never re-read it. Recent > OpenBSD changed to re-read resolv.conf when it is updated. I believe it > is useful specially for mobile environment. mdodd> The more useful solution is to run a local caching nameserver that mdodd> forwards to the DHCP or location specific nameservers. I was using this solution for several years, but I prefered to use totd. Since I thought this was overkill, I mode the patch. mdodd> I've got modifications to dhclient-script and a Makefile in /etc/namedb/ mdodd> that implement this behavior. I'll clean it up for public consumption if mdodd> others are interested. Not only dhclient updates resolv.conf, but ppp, mpd and perhaps others do. I'm using dhclient and ppp on my laptops. Sometimes, I use DHCPv6, too. So, I need such setting for each applications. It is messy to setup a laptop. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/