From owner-freebsd-questions@FreeBSD.ORG Fri Apr 4 04:08:58 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 D994437B401 for ; Fri, 4 Apr 2003 04:08:58 -0800 (PST) Received: from gs166.sp.cs.cmu.edu (GS166.SP.CS.CMU.EDU [128.2.205.169]) by mx1.FreeBSD.org (Postfix) with SMTP id 21FE843FBD for ; Fri, 4 Apr 2003 04:08:58 -0800 (PST) (envelope-from dpelleg@gs166.sp.cs.cmu.edu) Sender: dpelleg@gs166.sp.cs.cmu.edu To: "J. Seth Henry" References: <20030403224751.P74515-100000@whitetower.gambrl01.md.comcast.net> From: Dan Pelleg Date: 04 Apr 2003 07:08:38 -0500 In-Reply-To: <20030403224751.P74515-100000@whitetower.gambrl01.md.comcast.net> Message-ID: Lines: 43 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: questions@freebsd.org Subject: Re: dhclient acts odd with read-only '/' & other questions about /dev 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 12:08:59 -0000 "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