From owner-freebsd-current Mon Nov 4 17:47:45 2002 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 6114037B401; Mon, 4 Nov 2002 17:47:44 -0800 (PST) Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net [207.115.63.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB33843E4A; Mon, 4 Nov 2002 17:47:43 -0800 (PST) (envelope-from kbyanc@posi.net) Received: from gateway.posi.net (adsl-63-201-92-224.dsl.snfc21.pacbell.net [63.201.92.224]) by pimout2-ext.prodigy.net (8.12.3 da nor stuldap/8.12.3) with ESMTP id gA51lfpb306486; Mon, 4 Nov 2002 20:47:42 -0500 Received: from localhost (localhost [127.0.0.1]) by gateway.posi.net (8.12.6/8.12.5) with ESMTP id gA51ldOQ050769; Mon, 4 Nov 2002 17:47:39 -0800 (PST) (envelope-from kbyanc@posi.net) Date: Mon, 4 Nov 2002 17:47:39 -0800 (PST) From: Kelly Yancey To: "David O'Brien" Cc: Giorgos Keramidas , Hidetoshi Shimokawa , Doug Barton , , Subject: Re: Can't resolve hosts via dns on the command line with latest -current In-Reply-To: <20021105004300.GA48420@dragon.nuxi.com> Message-ID: <20021104174354.W50723-100000@gateway.posi.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 4 Nov 2002, David O'Brien wrote: > On Mon, Nov 04, 2002 at 10:45:42AM -0800, Kelly Yancey wrote: > > On Mon, 4 Nov 2002, Giorgos Keramidas wrote: > > > > > On 2002-11-04 01:16, Hidetoshi Shimokawa wrote: > > > > I have the same problem and reverting rev. 1.134 of > > > > /sys/kern/uipc_socket.c fixes the problem. > > > > The change might have something wrong with a loopback interface. > ... > > I've had this running on multiple machines for weeks without problems. What > > is your resolve.conf and nsswitch.conf? Curious, > > A better question is why you are fixing a non-critical, over-1-year-old > bug in networking code this close to the release??? Networking is our > bread and butter, and changes to it can be tricky. A known non-critical > bug that has existed at least since FBSD 4.2 is better than an unknown > one. At this point it time, it is better to just not touch things. > I'm not trying to fix a bug in ancient code. I'm trying to track down a very specific bug that is reported to be related to a commit I made last week. However, so far, I have not found how the two are related. I've just been trying to keep the people who are affected by the bug in the loop while I'm tracking it down. Kelly -- Kelly Yancey -- kbyanc@{posi.net,FreeBSD.org} Join distributed.net Team FreeBSD: http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message