From owner-freebsd-hackers Mon Dec 30 17:57: 0 2002 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 5788D37B401 for ; Mon, 30 Dec 2002 17:56:59 -0800 (PST) Received: from bodb.mc.mpls.visi.com (bodb.mc.mpls.visi.com [208.42.156.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B27E43E4A for ; Mon, 30 Dec 2002 17:56:54 -0800 (PST) (envelope-from hawkeyd@visi.com) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by bodb.mc.mpls.visi.com (Postfix) with ESMTP id 3A6194AC5; Mon, 30 Dec 2002 19:56:48 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.6/8.11.6) id gBV1ukw03272; Mon, 30 Dec 2002 19:56:46 -0600 (CST) (envelope-from hawkeyd) Date: Mon, 30 Dec 2002 19:56:46 -0600 (CST) Message-Id: <200212310156.gBV1ukw03272@sheol.localdomain> Mime-Version: 1.0 X-Newsreader: knews 1.0c.0 Reply-To: hawkeyd@visi.com Organization: if (!FIFO) if (!LIFO) break; References: <20021222071854.A86914_sheol.localdomain@ns.sol.net> <20021222154722.GA8522_happy-idiot-talk.infracaninophi@ns.sol.net> In-Reply-To: <20021222154722.GA8522_happy-idiot-talk.infracaninophi@ns.sol.net> From: hawkeyd@visi.com (D J Hawkey Jr) Subject: Re: Multi-threaded or async Mozilla (NSPR, really) X-Original-Newsgroups: sol.lists.freebsd.hackers To: m.seaman@infracaninophile.co.uk, freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii 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 In article <20021222154722.GA8522_happy-idiot-talk.infracaninophi@ns.sol.net>, m.seaman@infracaninophile.co.uk writes: > On Sun, Dec 22, 2002 at 07:18:54AM -0600, D J Hawkey Jr wrote: > >> I can't imagine what Moz is doing within it's DNS code, even with the >> serialized DNS lookups. If nslookup replies within fractions of a second, >> why doesn't Moz?? > > Take a look at look at the getaddrinfo(3) man page and then try doing > a look up of the AAAA or A6 records for the troublesome locations. After looking at the man page, and understanding all of ~35% of it, I'll ask this: Are you referring to the oft-mentioned, ill-configured, INET6 records in some DNS servers, or are you referring to less-than-correct code in FreeBSD's TCP/IP stack, or are NSPR's routines indeed flawed? I guess I'll ask this, too: is getaddrinfo(3) called by gethostbyname(3)? It's the latter that Mozilla/NSPR calls, and is the blamed culprit. For giggles, I disabled INET6 in the kernel, re- built and installed it, and the problem vanished. But this doesn't answer the question: Is it problematic DNS records, a problematic OS, or what? The second, I doubt... > Cheers, > Matthew Thanks, Dave -- Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message