From owner-freebsd-chat Wed May 3 18:44:26 2000 Delivered-To: freebsd-chat@freebsd.org Received: from server1.huntsvilleal.com (server1.huntsvilleal.com [63.147.8.7]) by hub.freebsd.org (Postfix) with ESMTP id 031DD37BF2D for ; Wed, 3 May 2000 18:43:54 -0700 (PDT) (envelope-from kris@hiwaay.net) Received: from barricuda.bsd.nws.net (kris.huntsvilleal.com [63.147.8.46]) by server1.huntsvilleal.com (8.9.3/8.9.3) with ESMTP id UAA18002 for ; Wed, 3 May 2000 20:21:21 -0400 Received: from localhost (localhost [127.0.0.1]) by barricuda.bsd.nws.net (8.9.3/8.9.3) with ESMTP id AAA85751; Wed, 3 May 2000 00:20:18 -0500 (CDT) (envelope-from kris@hiwaay.net) Date: Wed, 3 May 2000 00:20:18 -0500 (CDT) From: Kris Kirby To: Terry Lambert Cc: freebsd-chat@FreeBSD.ORG Subject: Re: Naw, Netscape doesn't have a memory problem! In-Reply-To: <200005022127.OAA00936@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > You are using the shared memory extension. > > Disable it; you can do this explicitly, or you can do this by > forcing NetScape to not use the UNIX domain socket; if it comes > in over the TCP/IP, it will not attempt to use the extension. By this do you mean loading the binary over the network (a la NIS/NFS) or by communication with X? This particular instance was run over the network, saturating a 10MBit line for about two hours. ----- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "Fate, it seems, is not without a sense of irony." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message