From owner-freebsd-questions Tue Jul 13 9:54: 0 1999 Delivered-To: freebsd-questions@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 4713014EB8 for ; Tue, 13 Jul 1999 09:53:55 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id JAA15025; Tue, 13 Jul 1999 09:52:59 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Tue, 13 Jul 1999 09:52:59 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: Mikhail Teterin Cc: questions@freebsd.org Subject: Re: how to stop dhclient from overwriting resolv.conf In-Reply-To: <199907131333.JAA81986@misha.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 13 Jul 1999, Mikhail Teterin wrote: > Amy Wennings once wrote: > > > You may be happier using dhcpc instead of dhclient. You can determine > > whether you wish the resolv.conf or host name overwritten with dhcpc. > > I was using it for a while before, but would rather use what is > installed by ``make world''... Thanks! You can also specify it with dhclient. Take a look at http://home.san.rr.com/freebsd/dhcp.html. You can set what options you want to receive using dhclient.conf. Then take a look at dhclient-script and see what gets set where. Then you can set the appropriate combination of flags in your dhclient.conf file. If worst comes to worst, you can always set the immutable flag on resolv.conf. :) man chflags if you need that info. Good luck, Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message