From owner-freebsd-chat Tue May 25 9: 1:16 1999 Delivered-To: freebsd-chat@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 70F74152C9 for ; Tue, 25 May 1999 09:01:11 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id SAA94629; Tue, 25 May 1999 18:00:56 +0200 (CEST) (envelope-from des) To: cjclark@home.com Cc: dpilgrim@uswest.net (Darren Pilgrim), doconnor@gsoft.com.au, freebsd-chat@FreeBSD.ORG, crh@outpost.co.nz, mark@borg.com Subject: Re: SETI@home has teams now! References: <199905251554.LAA06918@cc942873-a.ewndsr1.nj.home.com> From: Dag-Erling Smorgrav Date: 25 May 1999 18:00:54 +0200 In-Reply-To: "Crist J. Clark"'s message of "Tue, 25 May 1999 11:54:41 -0400 (EDT)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Crist J. Clark" writes: > That all said, I do kill setiathome during work hours (on work > machines). However, it has nothing to do with CPU usage. setiathome > eats about 14 MB of memory. On my 64 MB RAM PC here at work, that's > enough to cause some swapping, and _that_ can hit performance. Just SIGSTOP it. It'll get swapped out if you run low on memory. Then SIGCONT it when you leave work. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message