From owner-freebsd-current Mon Nov 4 19:27: 4 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 7A35137B401; Mon, 4 Nov 2002 19:27:03 -0800 (PST) Received: from pimout4-ext.prodigy.net (pimout4-ext.prodigy.net [207.115.63.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id B133C43E42; Mon, 4 Nov 2002 19:27:02 -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 pimout4-ext.prodigy.net (8.12.3 da nor stuldap/8.12.3) with ESMTP id gA53R1Q0488256; Mon, 4 Nov 2002 22:27:01 -0500 Received: from localhost (localhost [127.0.0.1]) by gateway.posi.net (8.12.6/8.12.5) with ESMTP id gA53QxOQ050969; Mon, 4 Nov 2002 19:26:59 -0800 (PST) (envelope-from kbyanc@posi.net) Date: Mon, 4 Nov 2002 19:26:59 -0800 (PST) From: Kelly Yancey To: "David O'Brien" Cc: freebsd-current@FreeBSD.org Subject: Re: Can't resolve hosts via dns on the command line with latest -current In-Reply-To: <20021105030237.GA49083@dragon.nuxi.com> Message-ID: <20021104191939.K50916-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 05:47:39PM -0800, Kelly Yancey wrote: > > > 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 was speaking of your commit last week to uipc_socket.c: > ---------------------------- > revision 1.134 > date: 2002-11-01 21:27:59; author: kbyanc; state: Exp; lines: +1 -1 > ... > PR: 30634 > ---------------------------- > > PR 30634 is over a year old and is classified as non-critical. > It was important to me. I ran into the problem independently and have been running the committed patches for 2 weeks on multiple machines. However, none of the machines made UDP connections via lo0 so I didn't spot the bug before commit. However, since commit I have seen 4 reports of people having trouble resolving via localhost, 2 of which claim the backing out the commit solves their problems. I'm actively tracking it down (as my numerous updates throughout the day should indicate) and if I don't find the problem soon I will revert the delta in question. This is code we use at work and I certainly want to fix the bug if it turns out to be related to my commit. Kelly -- Kelly Yancey -- kbyanc@{posi.net,FreeBSD.org} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message