From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Mon 28 Mar 2005 - 17:45:11 BST
On Mon, Mar 28, 2005 at 08:28:49PM +0400, Peter V. Saveliev wrote:
> ...
>
> Now I plan to migrate to 1.9.5 & 2.6.11, 'cause of resource limits; and I have
> some questions:
>
> 1) is it right, that I've to create one directory
>
> /etc/vservers/<vserver-name>/interfaces/<iface>
>
> per interface and there can be only one address on such interface?
yes, that's right, but that doesn't mean that you just can
have one address per interface, just more structured entries
> I didn't read the code, I'll do it while going to the home this
> night, but the answer will help me anyway.
> Now I use rewritten vserver (util 1.28), that adds
> addresses via iproute2, not ifconfig, so, I haven't any problems
> with address labels etc.
well, util-vserver (alpha tools) for 2.4 and 2.6 kernel
do the same if not told otherwise (using iproute2), the
alias thingy is more a legacy solution ...
> 2) where I can find documentation on
>
> /etc/vservers/<vserver-name>/rlimits/*
mainly 'man getrlimit' and the Flower Page (for the details
how the limits are named) ...
> syntax? Can I define hard limits on cpu & memory usage per context?
> E.g., I want context "bala.org" to use not more than 50% CPU time,
> roughly speeking.
that is what the token bucket scheduler is for ...
> Now I have to monitor vserver cluster and to stop a context manually
> (via script, anyway), when it consumes too much CPU or memory.
memory can be limited as VM, VML and RSS for now,
anon RSS might become a separate limit in the future
> 3) Now I use LVM, so there is no problems with disk quotas:
> there is only one context per partition.
disk quota as in disk limits ... I assume here
> Now I want my system to get smaller and plan to refuse
> LVM. Is there per context disk limits in 1.9.5?
yep per context disk limits on a shared partition are
part of the 1.9.x releases, you just have to use xid
tagged filesystems ...
> PS: package size and config simplicity are critical, so, I'll
> read new util-vserver code (at least shell scripts ;) anyway,
> and will patch it to fit my needs, as I did it before with 1.28.
just make sure to feed-back the changes, otherwise
other folks will end up reinventing your bicycle ;)
> But I don't wanna "invent a bicycle", so, thanks for any help.
>
> PPS: sorry my terrible English
well, we can communicate, what else matters?
HTH,
Herbert
> --
> Peter V. Saveliev
> _______________________________________________
> Vserver mailing list
> Vserver_at_list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver