From owner-freebsd-current@FreeBSD.ORG  Fri Oct 29 13:05:08 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 B30A416A4CE
	for <freebsd-current@freebsd.org>;
	Fri, 29 Oct 2004 13:05:08 +0000 (GMT)
Received: from mx1.imp.ch (mx1.imp.ch [157.161.9.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 97B5643D2F
	for <freebsd-current@freebsd.org>;
	Fri, 29 Oct 2004 13:05:07 +0000 (GMT)	(envelope-from mb@imp.ch)
Received: from mx2.imp.ch (mx2o [157.161.9.17])
	by mx1.imp.ch (8.12.11/8.12.11) with ESMTP id i9TD4oJG019077
	for <freebsd-current@freebsd.org>;
	Fri, 29 Oct 2004 15:04:52 +0200 (CEST)	(envelope-from mb@imp.ch)
Received: from mx2.imp.ch (localhost [127.0.0.1])
	by mx2.imp.ch (8.12.11/8.12.11/Submit) with ESMTP id i9TD4mku096369
	for <freebsd-current@freebsd.org>;
	Fri, 29 Oct 2004 15:04:49 +0200 (CEST)	(envelope-from mb@imp.ch)
Received: (from clamav@localhost)
	by mx2.imp.ch (8.12.11/8.12.11/Submit) id i9TD4maw096364
	for <freebsd-current@freebsd.org>;
	Fri, 29 Oct 2004 15:04:48 +0200 (CEST)	(envelope-from mb@imp.ch)
X-Authentication-Warning: mx2.imp.ch: clamav set sender to <mb@imp.ch> using
	-f
Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9])
	by ns1.imp.ch (MIMEDefang) with ESMTP id i9TD4hJh012446;
	Fri, 29 Oct 2004 15:04:48 +0200 (CEST)
Date: Fri, 29 Oct 2004 15:04:43 +0200 (CEST)
From: Martin Blapp <mb@imp.ch>
To: Tobias Roth <roth@iam.unibe.ch>
In-Reply-To: <20041029093840.GA19882@speedy.unibe.ch>
Message-ID: <20041029150420.C6222@cvs.imp.ch>
References: <20041028191324.GA18914@speedy.unibe.ch>
	<2231.1098990944@critter.freebsd.dk>
	<20041029093840.GA19882@speedy.unibe.ch>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Resent: Yes
X-Spam-Checksum: 82d10690bbdff86edae4614355631c77
X-Virus-Message-Status: No
X-Virus-Status: No, scantime="0.0015 seconds"
X-Spam-Status: No, hits=-4.9 required=5 scantime="10.2744 seconds"
	tests=BAYES_00
X-Scanned-By: MIMEDefang 2.45
cc: Poul-Henning Kamp <phk@phk.freebsd.dk>
cc: freebsd-current@freebsd.org
cc: Oliver Lehmann <lehmann@ans-netz.de>
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2004 13:05:08 -0000


Hi,

> stating that setting schg (as someone suggested to force a fixed dns)
> might be a bad idea, because dhclient used to get confused when it
> couldn't write to resolv.conf. i didn't test if this is still the
> current behaviour, though.

This is fixed in 5.x, but still a problem in 4.x.

Martin