From owner-freebsd-current Sat Apr 10 21:28:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id 42F2A15387 for ; Sat, 10 Apr 1999 21:28:49 -0700 (PDT) (envelope-from tr49986@rcc.on.ca) Received: from rcc.on.ca (24.66.20.80.on.wave.home.com [24.66.20.80]) by speed.rcc.on.ca (8.6.12/8.6.9) with ESMTP id BAA26445 for ; Sun, 11 Apr 1999 01:45:59 -0400 Message-ID: <37106B7D.50B2F49D@rcc.on.ca> Date: Sun, 11 Apr 1999 05:29:34 -0400 From: Rod Taylor X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: Re: DoS from local users (fwd) References: <199904110354.XAA28481@kot.ne.mediaone.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > What about a new login-class capability specifying the maximum > percentage of CPU time a class of users can utilize? With standard > class having 90% (or 95%)? The machine would appear (to most of > the users) as if it had 10% slower CPU, with the remaining usable > by the root-class. This way, if the CPU consumption by system is > 30%, the most CPU time the standard users can get is 60%. > > Trusted users can be placed into a different class, of course. > > Plausible? > I like this, but the problem with that fork bomb program still exists. It was afterall system cpu that was doing all the work, not the users cpu. I can however see how this could be useful for even myself. People who want to run eggdrops can have 40% cpu max on my shell server ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message