Re: [vserver] Ressources limits

Sam Przyswa wrote:
> Nikolay Kichukov a écrit :
>> hi,
>> the correct place would be:
>> /etc/vservers/<server-name>/rlimits/nofile
>>
>
> Thanks, when I check I got:
>
> vserver-1:~# cat /proc/virtual/40000/limit
> Limit current min/max soft/hard hits
> PROC: 53 0/ 112 -1/ -1 0
> VM: 576741 0/ 1431259 -1/ -1 0
> VML: 0 0/ 0 -1/ -1 0
> RSS: 64550 0/ 96015 -1/ -1 0
> ANON: 54704 0/ 83032 -1/ -1 0
> RMAP: 9846 0/ 18778 -1/ -1 0
> FILES: 489 0/ 662 65535/ 65535 0
> OFD: 203 0/ 203 -1/ -1 0
> LOCKS: 16 0/ 20 -1/ -1 0
> SOCK: 19 0/ 19 -1/ -1 0
> MSGQ: 0 0/ 0 -1/ -1 0
> SHM: 0 0/ 0 -1/ -1 0
> SEMA: 0 0/ 0 -1/ -1 0
> SEMS: 0 0/ 0 -1/ -1 0
> DENT: 631 0/ 722 -1/ -1 0
>
> But the ulimit -a give:
>
> zimbra:~# ulimit -a
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> scheduling priority (-e) 0
> file size (blocks, -f) unlimited
> pending signals (-i) 16382
> max locked memory (kbytes, -l) 64
> max memory size (kbytes, -m) unlimited
> open files (-n) 1024
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 8192
> cpu time (seconds, -t) unlimited
> max user processes (-u) unlimited
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
>
> As it's limit at 1024 as well as the vserver host.
>
> Is it right ?

ulimits and rlimits are not the same. rlimits apply to the entire guest,
ulimits apply to the process. Change /etc/vservers/<guest>/ulimits/nofile
as well to alter the ulimit value.

-- 
Daniel Hokka Zakrisson