When I do a:
% limit
I get:
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 kbytes
coredumpsize 0 kbytes
memoryuse unlimited <<----
descriptors 1024
memorylocked unlimited
maxproc 2047
openfiles 1024
We can see that memory use is unlimited, so it's natural that the thing
blows easily.
But you mean that even if I set memoryuse to a certain value smaller than
total memory in the system, I can still bomb it with malloc() because in
reality this isn't implemented?
C. Martins
On Thu, 6 Jul 2000, Marcelo Tosatti wrote:
>
> Per-user resource limits will avoid monkeys from doing that stuff.
>
> Unfortunately only 2.6 kernel will have this feature, but distribution
> vendors will probably use a backported version for 2.4.
>
> Linux per-user resource limits are called "user beancounters", and you can
> find a development version at www.asplinux.com.sg/install/ubpatch.html.
> Currently there is only kernel-level code.
>
> A userlevel PAM module is needed to make it usable for real systems.
>
> SGI's CSA (http://oss.sgi.com/projects/csa, no code available yet) is a
> similar, but more complete per-user resource accouting scheme which will
> be ported to Linux in the future.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jul 07 2000 - 21:00:20 EST