From owner-freebsd-current Mon Nov 4 16:48:35 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 01BD337B401; Mon, 4 Nov 2002 16:48:34 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8E7043E77; Mon, 4 Nov 2002 16:48:32 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.6/8.12.2) with ESMTP id gA50iGCE048601; Mon, 4 Nov 2002 16:44:16 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.6/8.12.6/Submit) id gA50h0ng048584; Mon, 4 Nov 2002 16:43:00 -0800 (PST) Date: Mon, 4 Nov 2002 16:43:00 -0800 From: "David O'Brien" To: Kelly Yancey Cc: Giorgos Keramidas , Hidetoshi Shimokawa , Doug Barton , freebsd-current@FreeBSD.org, kbyanc@FreeBSD.org Subject: Re: Can't resolve hosts via dns on the command line with latest -current Message-ID: <20021105004300.GA48420@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <20021104033637.GA5444@gray.sea.gr> <20021104104508.D50081-100000@gateway.posi.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021104104508.D50081-100000@gateway.posi.net> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 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, 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message