From owner-freebsd-stable Fri Dec 19 12:10:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA14166 for stable-outgoing; Fri, 19 Dec 1997 12:10:39 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from homer.duff-beer.com (mail@homer.duff-beer.com [194.207.51.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA14158 for ; Fri, 19 Dec 1997 12:10:32 -0800 (PST) (envelope-from scot@poptart.org) Received: from localhost (scot@localhost) by homer.duff-beer.com (8.8.5/8.8.5) with SMTP id UAA09092; Fri, 19 Dec 1997 20:09:46 GMT Date: Fri, 19 Dec 1997 20:09:46 +0000 (GMT) From: Scot Elliott To: Igor Roshchin cc: Scot Elliott , iang@digs.iafrica.com, stable@FreeBSD.ORG Subject: Re: fsck problem at boot time In-Reply-To: <199712191923.NAA17448@alecto.physics.uiuc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Dec 1997, Igor Roshchin wrote: > Setting CPU limit for users' processes would provide > automatic killing of such "fantoms" > (Note, that such pine starts eating lots of CPU cycles > for some reason, bringing the load index to 1 (if it was near 0 initially).) > Actually, I find this with Pine all the time too... is this a bug in pine? But my point about limiting daemon's CPU time still applies - you don't very often execute interactive processes as daemon. I hope. Scot ----------------------------------------------------------------------------- Scot Elliott (scot@poptart.org) | Work: +44 (0)1344 899401 PGP fingerprint: FCAE9ED3A234FEB59F8C7F9DDD112D | Home: +44 (0)181 8961019 ----------------------------------------------------------------------------- Public key available by finger at: finger scot@poptart.org or at: http://www.poptart.org/pgpkey.html