From owner-freebsd-current Thu Jan 27 21:32:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 4DAA815B93; Thu, 27 Jan 2000 21:32:12 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id AAA04649; Fri, 28 Jan 2000 00:32:10 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001280532.AAA04649@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001280222.SAA05076@mass.cdrom.com> Date: Fri, 28 Jan 2000 00:32:10 -0500 (EST) From: John Baldwin To: Mike Smith Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Cc: current@FreeBSD.org, "Jordan K. Hubbard" , obrien@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Jan-00 Mike Smith wrote: >> On Thu, Jan 27, 2000 at 04:20:54PM -0800, Mike Smith wrote: >> > >> > Actually, the problem here is that our dhclient doesn't pick the hostname >> > up the first time around. If it's set in an existing lease that is just >> > confirmed, it works, but if you're starting without a lease, you won't >> > get a hostname set (but it will be in the lease file, so if you restart >> > before the lease expires you're OK). >> >> Are you sure? In the case I know you experience, the server changed its >> behavior WRT handing out hostnames. I don't doubt that such a switch >> mid-stream in using DHCP would confuse things. > > Quite sure. I have several machines installed with the 26th snapshot > that aren't setting the hostname correctly. You were present when the > hostname issuing from the server problem was fixed, and the clients were > still not picking them up then. > >> > Personally I'd prefer to just fix the DHCP client so that it correctly >> > sets the hostname as obtained from the server... >> >> Nope. Poll larger shops first on their DHCP usage. > > Correct behaviour would be not to set the hostname unless: > > a) it is not already set > or > b) it was previously set by the DHCP client > > You could probably ignore b) and satisfy most people. At the moment, the > hostname is _never_ set by the DHCP client _unless_ it finds a lease that > is still valid. This is clearly a bug. Uh, no. It is set ok on the initial bootup. The lab of 30 or so FreeBSD machines I run at school use DHCP to get their hostnames and the current dhclient-script works perfectly: [0:28:21] (ttyp2) jobaldwi@raspberry:~ > grep hostname /etc/rc.conf hostname="" [0:28:27] (ttyp2) jobaldwi@raspberry:~ > grep host-name /var/db/dhclient.leases option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message