From owner-freebsd-hackers Wed Jan 22 7:19:35 2003 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81A1537B401 for ; Wed, 22 Jan 2003 07:19:34 -0800 (PST) Received: from pip.lemonia.org (pc-80-192-57-7-az.blueyonder.co.uk [80.192.57.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 4415643EB2 for ; Wed, 22 Jan 2003 07:19:32 -0800 (PST) (envelope-from lemon@aldigital.co.uk) Received: (qmail 68838 invoked from network); 22 Jan 2003 15:19:42 -0000 Received: from unknown (HELO aldigital.co.uk) (192.168.1.3) by 192.168.1.4 with SMTP; 22 Jan 2003 15:19:42 -0000 Message-ID: <3E2EB682.9040504@aldigital.co.uk> Date: Wed, 22 Jan 2003 15:19:30 +0000 From: lemon User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021126 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Pentchev Cc: freebsd-hackers@freebsd.org Subject: Re: getnameinfo contacting 'wrong' resolver for lookup References: <3E182B54.4090007@aldigital.co.uk> <20030122141615.GF379@straylight.oblivion.bg> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Pentchev wrote: > > My previous attempts at analyzing this aside, could this be related to > the problem described in PR bin/40984 and ports/39953? > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=40894 > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=39953 > the patch in the latter sorted the problem out, thanks for the pointer. it also explains why a little getnameinfo programlet never succeeded in reproducing the problem. echoing the comments in 40894, it'd be great if this made it into -STABLE. rgds, l. -- lemon@aldigital.co.uk +44 020 8742 0755 www.aldigital.co.uk system administrivia c6 h8 o7 www.thebunker.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message