From owner-freebsd-current Fri Feb 23 17:32:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by hub.freebsd.org (Postfix) with ESMTP id 15DC737B491 for ; Fri, 23 Feb 2001 17:32:54 -0800 (PST) (envelope-from camel@avias.com) Received: from 192.168.2.2 ([192.168.2.2]) by camel.avias.com (8.11.2/8.11.1) with ESMTP id f1O1Wgx38079 for ; Sat, 24 Feb 2001 04:32:43 +0300 (MSK) (envelope-from camel@avias.com) Date: Sat, 24 Feb 2001 04:34:51 +0300 From: Ilya Naumov X-Mailer: The Bat! (v1.48d) Educational Reply-To: Ilya Naumov X-Priority: 3 (Normal) Message-ID: <9220809782.20010224043451@avias.com> To: current@freebsd.org Subject: Re: name resolution problems In-reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Wesley, Tuesday, February 20, 2001, 1:26:29 AM, you wrote: WM> Since the big shake-up with -current, I find that mozilla and galeon can WM> no longer function (both up to date), but lynx has no problems. Mozilla WM> seems stuck resolving hostnames, yet tcpdump shows no traffic and truss WM> indicates that it is simply looping around a poll(). The biggest WM> difference between lynx and mozilla in terms of name resolution is that WM> mozilla is linked against libc_r... Could there be some problem here? WM> Is anyone else seeing this? yes, i see that too. but i experience the problem even with statically linked linux-opera from ports. very strange.. -- Best regards, Ilya mailto:camel@avias.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message