Re: 2.0, loggings, cpu quotas, 2.1 issues, etc.

Herbert Rosmanith (herp@wildsau.idv.uni-linz.ac.at)
Tue, 11 Jun 1996 20:14:34 +0200 (MET DST)

Matthias Urlichs writes about CPU% limitation:

> [..] (and kick the few people who can't understand the words "ce=
> ase and desist" off the system).
>

actually, a task can use 99,9% CPU without a malicious user sitting behind.
as an example, in a.out systems, where mapping to addr 0 is valid,
a strlen(NULL) or strcpy(NULL ...) can make a task use 99,9% CPU.
and since I am not watching the system 24 hours a day to terminate such
tasks (which may run as demons), CPU% limitation would help a bit....