Re: name resolution problems
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, Ilyamailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: name resolution problems
On 19 Feb, Wesley Morgan wrote: > Since the big shake-up with -current, I find that mozilla and galeon can > no longer function (both up to date), but lynx has no problems. Mozilla [...] > Is anyone else seeing this? Yes (galeon-0.9b3 + mozilla-0.7). Netscape 4.76 works. Bye, Alexander. -- ...and that is how we know the Earth to be banana-shaped. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: name resolution problems
On Mon, 19 Feb 2001, Wesley Morgan wrote: > Since the big shake-up with -current, I find that mozilla and galeon can > no longer function (both up to date), but lynx has no problems. Mozilla > seems stuck resolving hostnames, yet tcpdump shows no traffic and truss > indicates that it is simply looping around a poll(). The biggest > difference between lynx and mozilla in terms of name resolution is that > mozilla is linked against libc_r... Could there be some problem here? > Is anyone else seeing this? I see that too. I removed ~/.mozilla, and it works well, but only once. At next launch it get stuck in name resolution again, until I remove ~/.mozilla. Weird. Cheers, --fred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
name resolution problems
Since the big shake-up with -current, I find that mozilla and galeon can no longer function (both up to date), but lynx has no problems. Mozilla seems stuck resolving hostnames, yet tcpdump shows no traffic and truss indicates that it is simply looping around a poll(). The biggest difference between lynx and mozilla in terms of name resolution is that mozilla is linked against libc_r... Could there be some problem here? Is anyone else seeing this? -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
