Restricting CPU usage alone can be done relatively easily during
recalculate . Before renewing the counter for a task, a quick check could
be made against a newly added user-specific limit. If very precise
accounting is not needed, the check could be done by one of the periodic
daemons.....
But a bigger question remains : will doing this achieve the objective of
isolating a malicious/errant process ? There are a number of other system
resources that the process/user could overuse to the detriment of other
users/processes.
Shailabh
Eduardo Cortés <the_beast@softhome.net>@vger.kernel.org on 08/16/2001
03:22:55 PM
Sent by: linux-kernel-owner@vger.kernel.org
To: linux-kernel@vger.kernel.org
cc:
Subject: Re: Re: limit cpu
On Thursday 16 August 2001 20:54, you wrote:
> > If somebody want to develope it, a lot of thanks. I see scheduler could
> > be better with this feature, opinions?
>
> one excellent reason noone has bothered with it is that hardware
> is dirt cheap. it's extremely unusual these days to find a machine
> where hostile users are given shell accounts. for non-hostile
> situations (my lab, for instance), or for servers, the feature is
> useless.
at server level, this feature will be used for virtual hosts (a lot of
ISP's). Could be used at home for security reason limitting any user
95-97%,
and box will be more secure. A lot of people use applications (for XFree)
that could crash the box for this reason.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 23 2001 - 21:00:17 EST