From owner-freebsd-hackers Tue May 18 15:20:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (Postfix) with SMTP id 6311014D72 for ; Tue, 18 May 1999 15:20:24 -0700 (PDT) (envelope-from ab@paert.tse-online.de) Received: (qmail 87059 invoked by uid 1000); 18 May 1999 22:26:26 -0000 Date: Wed, 19 May 1999 00:26:26 +0200 From: Andreas Braukmann To: hackers@FreeBSD.ORG Subject: Re: Seti project / stats reset, new version available Message-ID: <19990519002626.D83255@paert.tse-online.de> References: <224739.3136033369@d225.promo.de> <37419AF0.93569574@softweyr.com> <19990518121747.A61302@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990518121747.A61302@dan.emsphone.com>; from Dan Nelson on Tue, May 18, 1999 at 12:17:48PM -0500 Organization: TSE TeleService GmbH Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, May 18, 1999 at 12:17:48PM -0500, Dan Nelson wrote: > Problem is that idprio isn't safe. I used to idprio the rc5client, but > within a day or do the machine would lock up. oops. That's new for me. I'm running the 'rc5client' on various machines (2.2.6-stable, 2.2.8-stable, 3.1-stable, 3.2-stable, 4.0-current) at the lowest idle priority. I had definately no problems so far. > Rc5client would get a > lock on the root of the filesystem at idprio, and if there was another > process running at 100% CPU, rc5client would never get a chance to ^^^^^^^^^^^^^^^^^^ at least 3 of the machines are on 'heavy cpu-duty' and are very used to run 100% cpu processes. (e.g. batch graphic filtering, 3D-rendering, etc.) > See PR kern/5641. I'll have a look ... -Andreas -- : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message