thanks herbert for your answer
nevertheless, ulimits of this type are supported and
will effect each task independantly, but as I said, I'm
relatively sure that this is not the case ...
There is no limits inside the vserver
[EMAIL PROTECTED] ~]$ ulimit -a|grep cpu
cpu time (seconds, -t) unlimited
How can I be sure that there no cpu limit on the vserver side ? How can
I see the cpu limit ?
PS: this might be worth inspecting on our side, which
kernel and patch version is it?
vserver-info
Versions:
Kernel: 2.6.16-1.2096_FC4.vs2.0.2.0.rc17.1smp
VS-API: 0x00020001
util-vserver: 0.30.210; Apr 15 2006, 20:07:50
Features:
CC: gcc, gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)
CXX: g++, g++ (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)
CPPFLAGS: ''
CFLAGS: '-O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -m32 -march=i386 -mtune=pentium4
-fasynchronous-unwind-tables -std=c99 -Wall -pedantic -W -funit-at-a-time'
CXXFLAGS: '-O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -m32 -march=i386 -mtune=pentium4
-fasynchronous-unwind-tables -ansi -Wall -pedantic -W -fmessage-length=0
-funit-at-a-time'
build/host: i686-redhat-linux-gnu/i686-redhat-linux-gnu
Use dietlibc: yes
Build C++ programs: yes
Build C99 programs: yes
Available APIs: compat,v11,fscompat,v13,net,oldproc,olduts
ext2fs Source: e2fsprogs
syscall(2) invocation: alternative
vserver(2) syscall#: 273/glibc
Paths:
prefix: /usr
sysconf-Directory: /etc
cfg-Directory: /etc/vservers
initrd-Directory: /etc/rc.d/init.d
pkgstate-Directory: /var/run/vservers
vserver-Rootdir: /vservers
_______________________________________________
Vserver mailing list
[email protected]
http://list.linux-vserver.org/mailman/listinfo/vserver
