From owner-freebsd-questions Wed Nov 22 18: 5:28 2000 Delivered-To: freebsd-questions@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2026037B479 for ; Wed, 22 Nov 2000 18:05:26 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAN25NT00357; Wed, 22 Nov 2000 18:05:23 -0800 (PST) Date: Wed, 22 Nov 2000 18:05:23 -0800 From: Alfred Perlstein To: Richard B Mahoney Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Restricting a users CPU usage -- Possible? Message-ID: <20001122180523.U18037@fw.wintelcom.net> References: <20001123144644.B42752@student.canterbury.ac.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001123144644.B42752@student.canterbury.ac.nz>; from rbm49@student.canterbury.ac.nz on Thu, Nov 23, 2000 at 02:46:45PM +1300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Richard B. Mahoney [001122 17:48] wrote: > Dear Readers, > > I know its possible to restrict user disk storage quotas under FreeBSD > but what about a user's CPU usage? I've searched for info on this and > have come up empty handed. The reason I ask is as follows. [snip] Well you can limit RAM usage via the login.conf(5) limiting facility. That ought to keep the programs from getting out of control and swamping the box. > The other day Emacs kept climbing in this way and exceeded the > available swap space. The system promptly stepped in and killed it by > itself! I was in many ways delighted. Under any other system and a > reboot would have been needed. Maybe we ought to switch the policy of out of memory so that the kernel will seek and destroy all emacs processes... :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message