From owner-freebsd-current@FreeBSD.ORG Wed Oct 27 21:13:42 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 B973516A4CE for ; Wed, 27 Oct 2004 21:13:42 +0000 (GMT) Received: from dill.salatschuessel.net (pD95FD812.dip.t-dialin.net [217.95.216.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6011843D31 for ; Wed, 27 Oct 2004 21:13:41 +0000 (GMT) (envelope-from lehmann@ans-netz.de) Received: (qmail 96551 invoked by uid 89); 27 Oct 2004 21:14:09 -0000 Received: from unknown (HELO kartoffel.salatschuessel.net) (olivleh1@dill.salatschuessel.net@10.0.1.51) by dill.salatschuessel.net with SMTP; 27 Oct 2004 21:14:09 -0000 Date: Wed, 27 Oct 2004 23:14:09 +0200 From: Oliver Lehmann To: freebsd-current@freebsd.org Message-Id: <20041027231409.436ce509.lehmann@ans-netz.de> In-Reply-To: <20041027205730.GA59489@dragon.nuxi.com> References: <20041027224512.2e3b2ae8.lehmann@ans-netz.de> <20041027204852.GY95878@horsey.gshapiro.net> <20041027205730.GA59489@dragon.nuxi.com> X-Mailer: Sylpheed version 0.9.99 (GTK+ 1.2.10; i386-portbld-freebsd4.10) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: dhclient trashes my resolv.conf 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: Wed, 27 Oct 2004 21:13:42 -0000 David O'Brien wrote: > "domain-name-servers" is one of the knobs want to tweak. So, there is a supersede, default, append and prepend statement, but nothing like "ignore". So that means, I've to configure my resolv.conf through dhclient.conf? How do I configure "options timeout:10" through dhclient.conf? And you allways must keep in mind to sync resolv.conf changed to your dhclient.conf. What, if my pppd modifies my resolv.conf? dhclient would kick that change away, right? I think there must sth. like a "don't rm -f my resolv.conf, it's not windows here!" configure switch somewhere like pppd has. It took me some time figuring wat happend first time to detect what killed my resolv.conf (at 1st I had problems with sshing to the system because reverse DNS for 10/8 didn't worked any longer). I just commented the function calls in dhclient-script out, but that will be lost with my next make installworld. -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/