From owner-freebsd-questions@FreeBSD.ORG Fri Apr 4 09:08:40 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9526637B401 for ; Fri, 4 Apr 2003 09:08:40 -0800 (PST) Received: from smtp-out.comcast.net (smtp-out.comcast.net [24.153.64.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id B621643FA3 for ; Fri, 4 Apr 2003 09:08:37 -0800 (PST) (envelope-from jshamlet@comcast.net) Received: from whitetower (bgp01561290bgs.gambrl01.md.comcast.net [68.50.33.221]) by mtaout10.icomcast.net (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id <0HCT0078PWNQIT@mtaout10.icomcast.net> for questions@freebsd.org; Fri, 04 Apr 2003 12:02:15 -0500 (EST) Date: Fri, 04 Apr 2003 12:02:14 -0500 (EST) From: "J. Seth Henry" In-reply-to: X-X-Sender: jshamlet@whitetower.gambrl01.md.comcast.net To: Dan Pelleg Message-id: <20030404120034.F80922-100000@whitetower.gambrl01.md.comcast.net> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT cc: questions@freebsd.org Subject: Re: dhclient acts odd with read-only '/' (SOLVED) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 17:08:40 -0000 That did it - I copied resolv.conf to /usr/local/etc and created a symlink. dhclient runs properly, and now I can remote reboot without making a visit. Now if I could just figure the /dev thing out... Thanks again for the help! Seth Henry On Fri, 4 Apr 2003, Dan Pelleg wrote: > "J. Seth Henry" writes: > > > Ok, I think I just qualified for an idiot award. After a little more > > poking around, I discovered that it was the read-only filesystem that was > > causing the problem. I rebuilt the microdrive image, and included a > > special /dev this time - which I mount over the original /dev. Now, I > > don't seem to be having any problems with sshd. > > > > Unfortunately, I appear to have made my dhclient problem worse. Now, it > > hangs, producing volumes of log data like this: > > > > Apr 3 17:52:45 dhclient: New IP Address (aue0): 192.168.1.5 > > Apr 3 17:52:45 dhclient: New Subnet Mask (aue0): 255.255.255.0 > > Apr 3 17:52:45 dhclient: New Broadcast Address (aue0): 192.168.1.255 > > Apr 3 17:52:45 dhclient: New Routers: 192.168.1.254 > > Apr 3 17:52:45 dhclient: New Network Number: 192.168.1.0 > > Apr 3 17:52:45 dhclient: New Broadcast Address: 192.168.1.255 > > Apr 3 17:52:45 dhclient: New IP Address (aue0): 192.168.1.5 > > Apr 3 17:52:45 dhclient: New Subnet Mask (aue0): 255.255.255.0 > > Apr 3 17:52:45 dhclient: New Broadcast Address (aue0): 192.168.1.255 > > Apr 3 17:52:45 dhclient: New Routers: 192.168.1.254 > > > > I have to hit CTRL-C to get a login... > > > > I tried running dhclient under truss, but it gives me a segmentation fault > > before getting very far. It doesn't seem to be attempting to write to > > files on a read-only filesystem though. I can post the output of truss if > > anyone is interested. > > > > I don't remember the history of this thread, but my first thought > would be that it's probably trying to update /etc/resolv.conf and/or > /var/db/dhclient.leases > > I don't think a failure to update resolv.conf would result in > this behaviour. But for dhclient.leases, it might. > > Advance warning: if you're using ntp, you will have a similar > issue for ntp.drift. > > -- > > Dan Pelleg >