From owner-freebsd-stable Mon Sep 6 18:38:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dns02.arpa-canada.net (dns02.arpa-canada.net [209.104.118.66]) by hub.freebsd.org (Postfix) with SMTP id AEBDB14E12 for ; Mon, 6 Sep 1999 18:38:08 -0700 (PDT) (envelope-from matt@MLINK.NET) Received: (qmail 52717 invoked by uid 1000); 7 Sep 1999 01:37:32 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Sep 1999 01:37:32 -0000 Date: Mon, 6 Sep 1999 21:37:32 -0400 (EDT) From: matt X-Sender: matt@dns02.arpa-canada.net To: aphor@ripco.com Cc: FreeBSD-stable@FreeBSD.ORG Subject: Re: System lockup In-Reply-To: <37D4698B.DBA448D8@ripco.NOSPAM.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had communicator 4.6 up for 3d10h now in X. I've had no problems running 3.2-Stable of Augest 24th. 128M ram 512M swap as well. I always leave communicator running as soon as I start X up. Saves me the trouble of waiting for it to load up when I need it. I'm sorry to say I don't know what your problem is, as communicator and -stable are fine over here. --Matt On Mon, 6 Sep 1999, Jeremy McMillan wrote: : : I have 128M RAM and 512M swap, and if I leave Communicator4.6 up for a long : period (two days?) it will take X out, and my system will reboot to boot. I : have issues with my CPU too, but Communicator brings out the worst in it :). : : I seriously doubt this is a STABLE issue. : : -- : PLEASE NOTICE: THERE MAY BE NOSPAM IN THE HEADERS WHEN YOU HIT "REPLY"!!! : Jeremy McMillan | Ask for PGP-2.6.2 or 5.0i : Chicago FreeBSD Users Group : http://pages.ripco.com/~aphor/ChiFUG.html : : : To Unsubscribe: send mail to majordomo@FreeBSD.org : with "unsubscribe freebsd-stable" in the body of the message : : -- // Matt Heckaman: matt@mlink.net -OR- admin@arpa-canada.net // // System Administrator/Owner: http://www.arpa-canada.net // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message