From owner-freebsd-current Wed Jan 27 07:33:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28144 for freebsd-current-outgoing; Wed, 27 Jan 1999 07:33:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA28136 for ; Wed, 27 Jan 1999 07:33:25 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 20706 invoked by uid 1001); 27 Jan 1999 15:33:23 +0000 (GMT) To: green@unixhelp.org Cc: asmodai@wxs.nl, current@FreeBSD.ORG Subject: RE: One answer, one question. In-Reply-To: Your message of "Wed, 27 Jan 1999 10:28:03 -0500 (EST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 27 Jan 1999 16:33:23 +0100 Message-ID: <20704.917451203@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In what sense do ye think VM_STACK is related to the Netscape issue? I'd > > love to hear what ye think causes it to bomb... > > I haven't really messed with it too much, so right now I think it's related > because testing makes it appear to be. i.e. if I have a kernel with VM_STACK > Netscape will sig11 right after loading; without VM_STACK it's as stable as > ever. I'd love to figure out why ps isn't working, though... Unfortunately, for some of us Netscape dying is not the problem. Netscape *hanging* is the problem. For me, it appears to be related to DNS lookups *and FreeBSD 3.0. If I run with MOZILLA_NO_ASYNC_DNS (ie. no DNS helper process), I often get hangs. This did not happen with FreeBSD 2.2.8. It appears to happen if name lookups take "too long". If I prime the cache on the DNS server (eg. by looking up the name manually beforehand), *or* if I let Netscape start a DNS helper process, I don't get these hangs. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message