Re: [Vserver] util-vserver + dietlibc ...
* Herbert Poetzl ([EMAIL PROTECTED]) wrote: > On Thu, Apr 07, 2005 at 12:14:48AM -0400, Paul S. Gumerman wrote: > > glibc seems to work fine. > > BTW what are the "Known issues" with glibc > > according to Enrico (please confirm or correct) > the glibc has issues with the fake name resolver > and is generally considered insecure because usually > dynamically linked ... This really needs further explanation and justification. What about glibc being dynamically linked (and able to load other libraries) makes it insecure, specifically? What changes would need to be done to make use of it secure? It seems to me that the main thing is to just avoid the situation in the code where you've chroot'd but have yet to finish and are calling functions. Basically, make sure you don't call any functions which could load up a library (this isn't hard, esp. as I'd expect the chroot call to be basically the very last thing that's done). I'm not actually 100% sure even that situation is a problem but it's the only thing I could think of that *might* be. The specific issue Enrico is concerned with really needs to be laid out and vetted. Stephen signature.asc Description: Digital signature ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] a couple of beginner questions
Hello Sig, [EMAIL PROTECTED] schrieb: 2) When I stop a vserver I get the following but it does infact stop. Any ideas as to how to correct this? sudo vserver-stat CTX PROCVSZRSS userTIME sysTIMEUPTIME NAME 0 32 33.5M 3K 0m35s20 0m30s27 16h26m54 root server 491874 7.4M 7670m00s14 0m00s60 1m06s54 crux03 sidenote: please don't use dynamic contexts for vserver guests, make them fixed ... sudo vserver crux03 stop vkill: vc_ctx_kill(): No such process in the vserver.stop script i have changed the line : $_VKILL -s INT -- "$initpid" || fail=1 to $_VKILL -c "$S_CONTEXT" -s INT -- "$initpid" || fail=1 Vserver '/usr/local/etc/vservers/crux03' still running unexpectedly; please investigate it manually... I think there is a problem with init based vservers. Maybe not in general but if the host is SuSE based. Vkill signals init to shutdown and immediately after that, vserver.stop tries to stop the vserver but the rc script is still running. I'm wrong ? Dieter this might be related to an issue we are investigating right now, is your guest init based? Thanks for the contexts tip. Not sure if I understand your question. Yes it uses init. Inside the vserver: ps -ef UIDPID PPID C STIME TTY TIME CMD root 1 0 0 08:35 ?00:00:00 init [2] root 24496 1 0 08:35 ?00:00:00 /usr/sbin/syslogd root 24509 1 0 08:35 ?00:00:00 /usr/sbin/crond root 24514 1 0 08:35 ?00:00:00 /usr/sbin/sshd ls -la /etc/inittab -rw-r--r-- 1 root root 604 Apr 4 12:09 /etc/inittab If you need anything else just let me know thanks sig ___ 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
Re: [Vserver] a couple of beginner questions
[EMAIL PROTECTED] schrieb: Herbert, I'm sorry, perhaps I've gotten off track. This goes back to the df command not working in the vserver. :df df: cannot read table of mounted filesystems Hello sig, in your vserver do 1) create the following mtab : /dev/hdv1 / ufs defaults 0 0 none /proc proc defaults 0 0 none /tmp tmpfs size=16m,mode=1777 0 0 none /dev/pts devpts gid=5,mode=620 0 0 - 2) delete the line /bin/rm -f /etc/mtab* from the etc/rc script Dieter ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
RE: [Vserver] a couple of beginner questions
Yes that works. I no longer get the warning. thanks sig -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of D. B. Sent: Wednesday, April 06, 2005 11:38 AM To: vserver@list.linux-vserver.org Subject: Re: [Vserver] a couple of beginner questions Hello Sig, [EMAIL PROTECTED] schrieb: >>>2) When I stop a vserver I get the following but it does infact stop. >>> Any ideas as to how to correct this? > > >>>sudo vserver-stat >>>CTX PROCVSZRSS userTIME sysTIMEUPTIME NAME >>>0 32 33.5M 3K 0m35s20 0m30s27 16h26m54 root server >>>491874 7.4M 7670m00s14 0m00s60 1m06s54 crux03 > > >>sidenote: please don't use dynamic contexts for vserver >>guests, make them fixed ... > > >>>sudo vserver crux03 stop >>>vkill: vc_ctx_kill(): No such process in the vserver.stop script i have changed the line : $_VKILL -s INT -- "$initpid" || fail=1 to $_VKILL -c "$S_CONTEXT" -s INT -- "$initpid" || fail=1 >>>Vserver '/usr/local/etc/vservers/crux03' still running unexpectedly; >>>please investigate it manually... I think there is a problem with init based vservers. Maybe not in general but if the host is SuSE based. Vkill signals init to shutdown and immediately after that, vserver.stop tries to stop the vserver but the rc script is still running. I'm wrong ? Dieter > > >>this might be related to an issue we are investigating >>right now, is your guest init based? > > > Thanks for the contexts tip. > > Not sure if I understand your question. Yes it uses init. > Inside the vserver: > ps -ef > UIDPID PPID C STIME TTY TIME CMD > root 1 0 0 08:35 ?00:00:00 init [2] > root 24496 1 0 08:35 ?00:00:00 /usr/sbin/syslogd > root 24509 1 0 08:35 ?00:00:00 /usr/sbin/crond > root 24514 1 0 08:35 ?00:00:00 /usr/sbin/sshd > > ls -la /etc/inittab > -rw-r--r-- 1 root root 604 Apr 4 12:09 /etc/inittab > > If you need anything else just let me know > thanks > sig > ___ > 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 ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
RE: [Vserver] a couple of beginner questions
Dieter, Yes that works perfectly. I spoke with Herbert last night and he came up with the same conclusion. thanks for your reply sig -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of D. B. Sent: Thursday, April 07, 2005 10:46 AM To: vserver@list.linux-vserver.org Subject: Re: [Vserver] a couple of beginner questions [EMAIL PROTECTED] schrieb: > Herbert, > > I'm sorry, perhaps I've gotten off track. This goes back to the df command > not working in the vserver. > > :df > df: cannot read table of mounted filesystems > Hello sig, in your vserver do 1) create the following mtab : /dev/hdv1 / ufs defaults 0 0 none /proc proc defaults 0 0 none /tmp tmpfs size=16m,mode=1777 0 0 none /dev/pts devpts gid=5,mode=620 0 0 - 2) delete the line /bin/rm -f /etc/mtab* from the etc/rc script Dieter ___ 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
[Vserver] Request for comments: Crux vserver install notes
I have vserver up and running on Crux linux. Below are my install notes. Any errors I have will (hopefully) get smoothed over on my next installation. Feel free to make comments / use this document if you desire. thanks sig How to install and use vserver with Crux 2.0 http://crux.nu/ http://linux-vserver.org/ Notes: Expect to find errors I may be doing things completely backwards but it seems to work vservers are going to be installed onto seperate partition /vservers I use sudo for most root commands. If you prefer to use root then ignore sudo at front of commands ## # #Preparing your host server with vserver # ## #Get vserver code cd ~/src/vserver wget http://www.13thfloor.at/vserver/d_rel26/v1.9.5/util-vserver-0.30.204.tar.gz gzip -d util-vserver-0.30.204.tar.gz tar -xf util-vserver-0.30.204.tar wget http://www.13thfloor.at/vserver/d_rel26/v1.9.5/linux-vserver-1.9.5.tar.gz gzip -d linux-vserver-1.9.5.tar.gz tar -xf linux-vserver-1.9.5.tar # Get vanilla linux kernel and compile in vserver patch aquired from above cd /usr/src sudo wget ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.11.5.tar.bz2 sudo bzip2 -d linux-2.6.11.5.tar.bz2 tar -xf linux-2.6.11.5.tar cd linux-2.6.11.5 sudo cp ../linux-2.6.6/.config . sudo cp ~/src/vserver/patch-2.6.11.5-vs1.9.5.diff sudo patch -p1 -s <../patch-2.6.11.5-vs1.9.5.diff sudo make menuconfig sudo make all sudo make modules_install #Install newly patched kernel cd /usr/src sudo rm linux sudo ln -s linux-2.6.11.5 linux sudo cp /usr/src/linux-2.6.11.5/arch/i386/boot/bzImage /boot/vmlinuz-2.6.11.5-1 sudo cp System.map /boot/System.map-2.6.11.5-1 cd /boot sudo ls -s System.map-2.6.6-2 System.map sudo vi /etc/lilo.conf ... ... image=/boot/vmlinuz-2.6.11.5-1 label=KERNEL-4 root=/dev/discs/disc0/part2 read-only sudo lilo -q sudo lilo sudo lilo -q #Install additional/required software sudo prt-get install iproute2 sudo prt-get install iptables sudo prt-get install rsync #Get vconfig binary cd ~/src/ wget http://www.candelatech.com/~greear/vconfig sudo cp vconfig /usr/local/sbin #Complile and install vserver utilities cd ~/src/vserver/util-vserver-0.30.204 ./configure --prefix=/usr/local make sudo make install #Create vserver guest OS directory sudo mkdir -m 000 /vservers sudo mkdir /vservers/vcrux01 #If using SSH (or any other port listening application) change it to listen to the specific interface (ie not 0.0.0.0) sudo vi /etc/ssh/sshd_config ... ... ListenAddress 172.27.12.19 ... ... #restart ssh and ensure it still works sudo /etc/rc.d/sshd restart ## # #Building your first vserver # ## sudo vserver vcrux01 build -m skeleton -n vcrux01 --context 100 --hostname vcrux01.domain.net --interface 172.27.12.24 --netdev eth0 --netmask 255.255.248.0 --initstyle plain #Set up vserver barrier sudo showattr -d /vservers ---bui- /vservers sudo setattr --barrier /vservers sudo showattr -d /vservers ---Bui- /vservers #I don't think this is required anymore #sudo chmod /vservers #set default tty (not sure if this works) sudo mkdir -p /usr/local/etc/vservers/.defaults/apps/init cd /usr/local/etc/vservers/.defaults/apps/init sudo ln -s /dev/tty6 tty #Check the folowing files to ensure all it configured fine. If not edit files. cat /usr/local/etc/vservers/vcrux01/apps/init/style plain cat /usr/local/etc/vservers/vcrux01/interfaces/dev eth0 cat /usr/local/etc/vservers/vcrux01/interfaces/mask 255.255.248.0 cat /usr/local/etc/vservers/vcrux01/interfaces/0/ip 172.27.12.24 cat /usr/local/etc/vservers/vcrux01/interfaces/0/name c01 cat /usr/local/etc/vservers/vcrux01/uts/nodename vcrux01.domain.net cat /usr/local/etc/vservers/vcrux01/name vcrux01 cat /usr/local/etc/vservers/vcrux01/fstab none/proc procdefaults0 0 none/tmptmpfs size=16m,mode=1777 0 0 none/dev/ptsdevpts gid=5,mode=620 0 0 cat /usr/local/etc/vservers/crux01/context 100 ## # #Install Crux to /vserver/vcrux01 # ## #boot from crux install cd #mount /, /usr, and /vservers to /mnt, /mnt/usr, and /mnt/vservers #chroot to /mnt #set root password #run crux setup #use /mnt/vservers/vcrux01 as install point #do not compile kernel, not used #do not run lilo #do not run lilo #do not run lilo #see crux handbook for details: http://crux.nu/doc/handbook.html #boot OS back up #configure guest OS vcrux01 cd /mnt/vservers/vcrux01 sudo vi ./etc/rc.conf TIMEZONE=Canada/Mountain HOSTNAME=vcrux01 SERVICES=(crond sshd) sudo rm -f ./etc/mtab sudo vi ./etc/mtab /dev/hdv1 / ufs rw 0 0 sudo chmod 644 ./etc/mtab sudo vi ./etc/rc #At the very least comment out: #/bin/rm -f /etc/mtab* #null this file out cat /dev/null > ./etc/fstab sudo vi ./etc/hosts.allow sshd:all cat /dev/null > ./etc/rc.d/net sudo vi ./etc/resolve.conf domain domain.net search
[Vserver] Plesk
Title: Message Did anyone try to run plesk 7.5 reloaded recently under vserver in a production server? Tried it long ago but had some problems, i think it wanted some kind of physical control over ips or network card and something to do with loopback. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ehab HeikalSent: Thursday, April 07, 2005 4:56 AMTo: vserver@list.linux-vserver.orgSubject: RE: [Vserver] CentOs distribution Fedora is experimental, you do not want the latest and coolest software on your server, you need the most stable. This is what CENTOS and RHEL give you older more stable software like good wine. The main difference between an enterprise grade system and just plain old software is that you get the bug fixes for the old software for a long time. Thus the stability. CENTOS is close to perfect, the main problem is that there are many customizations to the RH kernel over the plain vannilla kernel.org kernel that vserver does not compile for RH kernels, how much of that will affect you if you run a plain kernel on a RH disti, well that is more or less unknown you always run the risk of getting an arcane error that happens only to you. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul S. GumermanSent: Wednesday, April 06, 2005 8:07 PMTo: vserver@list.linux-vserver.orgSubject: Re: [Vserver] CentOs distributionMy thoughts exactly! I'll be doing a test install today, then patching a kernel for drbd + linux-vserver.Daniel S. Reichenbach wrote: Hi, This may be somewhat off-topic, but why is it that people like centos which seems to me like REL without support. Since support is what REL is all about, wouldn't it be better to go with FC3 (soon 4) rather than a bunch of outdated software that comprises EL? What am I missing? Fedora Core is updating packages way to fast. While I believe it is fine for personal use to always have the latest version of a package, in business it seems more appropriate to have a working version and only upgrade for security reasons or bug fixes - which is what also differs RHEL from FC - and upgrade to newer versions only if it has significant benefits to offer. I have tried to use Fedora Core for business projects, but this is not a Good Thing(tm). Since I am using FC since its first release, I have noticed, they release packages breaking backward compatibility or even the complete system at least every fourth month. While the rate has lowered, it still is to high for professional use I'd say. IMHO for business projects you need systems where you can say they will run for two or three years without flaws. This is what RHEL offers with support and CentOS without support. With kind regards, Daniel S. Reichenbach ___ 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
Re: [Vserver] a couple of beginner questions
On Wed, Apr 06, 2005 at 07:38:23PM +0200, D. B. wrote: > Hello Sig, > > [EMAIL PROTECTED] schrieb: > >>>2) When I stop a vserver I get the following but it does infact stop. > >>> Any ideas as to how to correct this? > > > > > >>>sudo vserver-stat > >>>CTX PROCVSZRSS userTIME sysTIMEUPTIME NAME > >>>0 32 33.5M 3K 0m35s20 0m30s27 16h26m54 root server > >>>491874 7.4M 7670m00s14 0m00s60 1m06s54 crux03 > > > > > >>sidenote: please don't use dynamic contexts for vserver > >>guests, make them fixed ... > > > > > >>>sudo vserver crux03 stop > >>>vkill: vc_ctx_kill(): No such process > > in the vserver.stop script i have changed the line : > > $_VKILL -s INT -- "$initpid" || fail=1 > to > $_VKILL -c "$S_CONTEXT" -s INT -- "$initpid" || fail=1 this was recently improved/changed (and will be in 1.9.6) in the following way: - kill or vkill to the initpid will be blocked (this is part of the 'usual' init protection) - vkill with pid=1 to context will reach the init so this will have to change to $_VKILL -c "$S_CONTEXT" -s INT -- 1 > >>>Vserver '/usr/local/etc/vservers/crux03' still running unexpectedly; > >>>please investigate it manually... > > I think there is a problem with init based vservers. > Maybe not in general but if the host is SuSE based. > Vkill signals init to shutdown and immediately after that, > vserver.stop tries to stop the vserver but the rc script is still > running. > I'm wrong ? don't really, know ... we suspect that killall5 killst the init process too (which terminates the initscripts) but that might be wrong ... HTH, Herbert > Dieter > > > > > > >>this might be related to an issue we are investigating > >>right now, is your guest init based? > > > > > >Thanks for the contexts tip. > > > >Not sure if I understand your question. Yes it uses init. > >Inside the vserver: > >ps -ef > >UIDPID PPID C STIME TTY TIME CMD > >root 1 0 0 08:35 ?00:00:00 init [2] > >root 24496 1 0 08:35 ?00:00:00 /usr/sbin/syslogd > >root 24509 1 0 08:35 ?00:00:00 /usr/sbin/crond > >root 24514 1 0 08:35 ?00:00:00 /usr/sbin/sshd > > > >ls -la /etc/inittab > >-rw-r--r-- 1 root root 604 Apr 4 12:09 /etc/inittab > > > >If you need anything else just let me know > >thanks > >sig > >___ > >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 ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Request for comments: Crux vserver install notes
On Thu, Apr 07, 2005 at 12:31:48PM -0600, [EMAIL PROTECTED] wrote: > > I have vserver up and running on Crux linux. Below are my install notes. > Any errors I have will (hopefully) get smoothed over on my next installation. > Feel free to make comments / use this document if you desire. > > thanks > sig > > > > How to install and use vserver with Crux 2.0 > http://crux.nu/ > http://linux-vserver.org/ > > Notes: > Expect to find errors > I may be doing things completely backwards but it seems to work > vservers are going to be installed onto seperate partition /vservers > I use sudo for most root commands. If you prefer to use root then > ignore sudo at front of commands > > > ## > # > #Preparing your host server with vserver > # > ## > > #Get vserver code > cd ~/src/vserver > wget > http://www.13thfloor.at/vserver/d_rel26/v1.9.5/util-vserver-0.30.204.tar.gz > gzip -d util-vserver-0.30.204.tar.gz > tar -xf util-vserver-0.30.204.tar comment: why not bz2 here too? > wget http://www.13thfloor.at/vserver/d_rel26/v1.9.5/linux-vserver-1.9.5.tar.gz > gzip -d linux-vserver-1.9.5.tar.gz > tar -xf linux-vserver-1.9.5.tar comment: why not the patch for the specific kernel? > # Get vanilla linux kernel and compile in vserver patch aquired from above > cd /usr/src > sudo wget ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.11.5.tar.bz2 > sudo bzip2 -d linux-2.6.11.5.tar.bz2 > tar -xf linux-2.6.11.5.tar > > cd linux-2.6.11.5 > sudo cp ../linux-2.6.6/.config . > sudo cp ~/src/vserver/patch-2.6.11.5-vs1.9.5.diff > sudo patch -p1 -s <../patch-2.6.11.5-vs1.9.5.diff > > sudo make menuconfig > sudo make all note: no need to build the kernel as root IIRC > sudo make modules_install > > #Install newly patched kernel > cd /usr/src > sudo rm linux > sudo ln -s linux-2.6.11.5 linux > > sudo cp /usr/src/linux-2.6.11.5/arch/i386/boot/bzImage > /boot/vmlinuz-2.6.11.5-1 > sudo cp System.map /boot/System.map-2.6.11.5-1 should have same name as the kernel uses (I doubt you added -1?) > cd /boot > sudo ls -s System.map-2.6.6-2 System.map > > sudo vi /etc/lilo.conf > ... > ... > image=/boot/vmlinuz-2.6.11.5-1 > label=KERNEL-4 > root=/dev/discs/disc0/part2 > read-only > > sudo lilo -q > sudo lilo > sudo lilo -q > > #Install additional/required software > sudo prt-get install iproute2 > sudo prt-get install iptables > sudo prt-get install rsync > > #Get vconfig binary > cd ~/src/ > wget http://www.candelatech.com/~greear/vconfig what's that? does crux not support vlans? > sudo cp vconfig /usr/local/sbin > > #Complile and install vserver utilities > cd ~/src/vserver/util-vserver-0.30.204 > ./configure --prefix=/usr/local > make > sudo make install > > #Create vserver guest OS directory > sudo mkdir -m 000 /vservers > sudo mkdir /vservers/vcrux01 > > #If using SSH (or any other port listening application) change it to listen > to the specific interface (ie not 0.0.0.0) > sudo vi /etc/ssh/sshd_config > ... > ... > ListenAddress 172.27.12.19 > ... > ... > > #restart ssh and ensure it still works note: on a remote system, try first with a different port and in debug mode ... > sudo /etc/rc.d/sshd restart > > > ## > # > #Building your first vserver > # > ## > > > sudo vserver vcrux01 build -m skeleton -n vcrux01 --context 100 --hostname > vcrux01.domain.net --interface 172.27.12.24 --netdev eth0 --netmask > 255.255.248.0 --initstyle plain > > #Set up vserver barrier > sudo showattr -d /vservers > ---bui- /vservers > sudo setattr --barrier /vservers nitpick: setattr --barrier /vservers/vcrux01/.. is better > sudo showattr -d /vservers > ---Bui- /vservers > > #I don't think this is required anymore > #sudo chmod /vservers that would be a bad idea anyway ... > #set default tty (not sure if this works) > sudo mkdir -p /usr/local/etc/vservers/.defaults/apps/init > cd /usr/local/etc/vservers/.defaults/apps/init > sudo ln -s /dev/tty6 tty > > #Check the folowing files to ensure all it configured fine. If not edit > files. > cat /usr/local/etc/vservers/vcrux01/apps/init/style > plain > > cat /usr/local/etc/vservers/vcrux01/interfaces/dev > eth0 > > cat /usr/local/etc/vservers/vcrux01/interfaces/mask > 255.255.248.0 > > cat /usr/local/etc/vservers/vcrux01/interfaces/0/ip > 172.27.12.24 > > cat /usr/local/etc/vservers/vcrux01/interfaces/0/name > c01 only required if you like aliases ... > cat /usr/local/etc/vservers/vcrux01/uts/nodename > vcrux01.domain.net > > cat /usr/local/etc/vservers/vcrux01/name > vcrux01 > > cat /usr/local/etc/vservers/vcrux01/fstab > none/proc procdefaults0 0 > none/tmptmpfs size=16m,mode=1777 0 0 > none/dev/ptsdevpts gid=5,mode=620 0 0 > > cat /usr/local/etc/vservers/crux01/context > 100 > > > ## > # > #Install Crux t
[Vserver] Update on Debian kernel 2.6.8-15 and vs1.9.5
Here is an update of more hacking done to port the vserver 1.9.5 patches to the debian 2.6.8 kernel. I've applied Bertl's second attempt at the patch ;) to the Debian 2.6.8-15 kernel-source tree, configured everything (including vserver and kernel debugging options), compiled and installed the kernel. Everything has been stable so far. Tonight we tested a few of the TODO items: . Uptime virtualization test Uptime virtualization will cause the context to account all process times and the uptime relative to the the context starting. When you do not have the virtualized uptime flag set, the uptime in a context is the host's uptime. It was not expected that this test would work, but we wanted to know for sure. The test: chcontext --ctx 100 --flag ^17 bash -c "sleep 600 & sleep 500; uptime; ps auxwww" This will change context to 100, set the uptime virtualization flag, and then run two sleeps (the first in the background). If it is working it should show something like 8 minutes uptime and the process start time for the backgrounded sleep should be 8 minutes back, and the current time for the "ps auxwww". Result: The uptime worked, but the ps time was wrong Bertl created new patches which should fix most of the issues (possibly including the uptime), and incorporates all fixes waiting for 1.9.6: http://vserver.13thfloor.at/Experimental/patch-2.6.8-15-vs1.9.5.x-3.diff http://vserver.13thfloor.at/Experimental/delta-2.6.8-15-vs1.9.5.x-2-3.diff (second is a delta between the -2 and the first) Three major things will not be included in this Debian version: - varhz: this changes the timer interrupt the kernel uses (was 100Hz for 2.4 and now is 1000Hz) the varhz allows you to change it between 20 and 2 Hz, this reduces the slice time for interactive servers and/or decreases the scheduling overhead. It didn't make a really big difference so it probably will go away soon. - the memory split for x86: memory split simply doesn't work before 2.6.9*/10 (this allows to have other memory splits on i386 other than 3/1 which allows to have more than 1GB memory without himem. For example systems with 2GB memory using highmem for them will add significant overhead, avoiding that with a 2/2 split is simply an advantage - bind mount extensions: http://lwn.net/Articles/124482/ bind bind mount extentions exist for 2.6.8, but are very different than the ones used for 2.6.11+, so they aren't included, if they are desired, then you should use the older patches, or move on to the 2.6.11 kernel TODO: . Test the -3 version of the patches . Need to check task_state (in proc) regarding initpid virtualization (means /proc//stat(us) . Need to check ext2/ext3 xattr with disk limit accounting . Need to test NFS . Need to test other basic capabilities (http://linux-vserver.org/Linux-VServer-Paper-14) ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
