From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Mon 08 Aug 2005 - 22:27:04 BST
On Sat, Aug 06, 2005 at 05:53:30PM +0200, Andreas John wrote:
> Dariush Pietrzak,,, wrote:
> > Good luck to all!
> Do I get it right, that there is no possibility to set per guest ulimits
> in the conf of vs20? I only found the possibility to set a "ulimit" or
> "nproc" flag in /etc/vservers/<foo>/flags, which is only for appying the
> current (i.e. the hosts) ulimit to the guest. I guess there can only be
> one ulimit in the (host) kernel, in our particular case for user "root",
> so all guests share one common umlinit unless it set "nproc" in the flags?
A directory with ulimits. Possible resources are cpu, data, fsize,
locks, memlock, nofile, nproc, rss and/or stack.
A directory with resource limits. Possible resources are cpu, fsize,
data, stack, core, rss, nproc, nofile, memlock, as and locks. This
configuration will be honored for kernel 2.6 only.
and from the 0.30.208 changelog:
2005-07-15 21:01 Enrico Scholz <enrico.scholz_at_informatik.tu-chemnitz.de>
* scripts/: vserver.start, vserver.suexec:
readded the limit-ulimits-per-vserver stuff due popular request
so the essential answers are:
- yes, you _can_ set ulimits for 2.6 kernels
- no, you don't want to use nproc or ulimit as flag
- usually you want to set rlimits not ulimits
(because the ulimits are controlled by the distro)
> Limit the number of process in the vserver according to ulimit setting.
> Normally, ulimit is a per user thing. With this flag, it becomes a per
> vserver thing.
this was true about 1 year ago, it should also be supported
to some extend by the legacy tools .. but in general, you
do not want to use/have it nowadays ...
> So, if I want to keep the guests umlimit reasonably low, I have to set
> the ulimit for root low????
no, see answer above ...
> Vserver mailing list
Vserver mailing list