On Sat, Aug 06, 2005 at 04:39:10PM +0200, Dariush Pietrzak,,, wrote:
> > Well, I mean if I run a mem-eater or process-rabbit within a guest, the
> > host's power drain up to total trashing (kudos the remote hands in the
> > datacentre)
> [EMAIL PROTECTED]:/tmp/PERL$ ulimit -l 10240 -m 10240 -u 12 -v 10240 -d 10240
> [EMAIL PROTECTED]:/tmp/PERL$ :(){ :|:&};:
> [1] 27182
> [EMAIL PROTECTED]:/tmp/PERL$ -su: fork: Resource temporarily unavailable
> -su: fork: Resource temporarily unavailable
>
> You just put that in vserver's guest configuration:
>
> grep -i ulimit /etc/vservers/dev.conf
> ULIMIT="-H -u 256 -n 1024"
actually those are ulimits, and they can be set on
2.4 and 2.6 based kernels (with legacy and recent tools)
but I guess he was talking about the rlimits, which
do not exist on 2.4 linux-vserver patches and are not
supported by legacy tools and config ...
> similiar thing works for dreaded new-style configuration (probably in
> /etc/vservers/dev/ulimit/*)
so actually it _only_ works with the (new-style )config
and with /etc/vservers/<name>/rlimit/...
best,
Herbert
> --
> Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9
> Total Existance Failure
> _______________________________________________
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
