Re: [Vserver] Problems with Knoppix 5.2 (which should be Vserver-enabled...)
Hi Gerhard, I just tested the knoppix cd you mentioned. I could install a vserver without problems. Could it be that you started the knoppix-system with the normal knoppix-kernel instead of the vserver-enabled one? Gruß, Alexander Am Mittwoch, 21. März 2007 17:03 schrieb Gerhard Hofmann: Hi all, I have some Vserver hosts running that were setup according to this HowTo: http://www.howtoforge.com/linux_vserver_debian Because these are quite a lot of steps I always thought it would be nice to have a Debian distro that is Vserver-enabled out-of-the-box. Now, in the recenct release of German magazine c't, there was a Knoppix 5.2 CD which claims to be Vserver-ready. Has anybody here already tried Knoppix 5.2 and can share his or her experiences? I booted Knoppix, tried to setup a Vserver like this: vserver vserver1 build \ -n vserver1 \ --hostname vserver1 \ --interface eth0:192.168.1.133/24 \ -m debootstrap -- -d sarge I get this error message: /etc/vservers/.defaults/vdirbase/vserver1: Function not implemented Any ideas? Or any other Vserver-ready distro out there? TIA Gerhard ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver -- netzwerk- systemadministrator --- lieblinx we do software --- agoeres at lieblinx. net http://lieblinx.net tel.: +49 (0)30 / 62 90 81 05 fax: +49 (0)30 / 61 20 26 87 reichenberger straße 125 10999 berlin --- geschäftsführer: fabian thiele, stefan kausch sitz der gesellschaft: berlin amtsgericht: berlin charlottenburg handelsregistereintrag HRB 97554 B ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] a question regarding disk limits
Am Dienstag, 16. Januar 2007 23:15 schrieb Herbert Poetzl: On Tue, Jan 16, 2007 at 04:04:51PM +0100, alexander goeres - lieblinx GmbH wrote: Hello List! I'm trying to make the disk-limits work for my vservers to gain some flexibility and ran into a problem: the disk limits seem to be disfunctional. I wonder if anyone could help me with that .. I followed the instructions provided on http://oldwiki.linux-vserver.org/Disk+Limits: - created a directory /etc/vservers/test1/dlimit/0 - in there I created the files space_total with 716800, inode_total with 10, reserved with 5 and directory with /var/lib/vservers/test - I was tagging the files in /var/lib/vservers: chxid -r --xid /var/lib/vservers/test When I reduced the space_total to an amount smaller than the actual vserver content vserver test start refused to come up, complaining that there is not enough space. After adjusting the space, the vserver could be started. Doing a df -kh inside the vserver gave: FilesystemSize Used Avail Use% Mounted on /dev/hdv1 700M 579M 87M 88% / Until here everything looks fine. The error showed, when inside this vserver I succeed doing a: dd if=/dev/zero of=testfile bs=1M count=1024 This produced a 1 GB big file inside the vserver that claimed to have only 87 MB left. not that unusal, disk limits are only implemented for ext2/3/4, reiserfs and jfs for now, so xfs is not accounted and thus not limited .. Perfect, so i just picked the wrong fs ... Are the disk limits functional? yes, they are working quite fine for the supported filesystems ... If yes, how are they to be set up? The setup was simplified with recent tools, which do now calculate the used space and save/restore the current values and limits properly No complaints about the setup from me. If it works it could hardly be easier ... so what you described should work fine for the supported filesystems ... Any advice is appreciated. The vserver-version is a vanilla kernel 2.6.19.2 with vs 2.2.0-rc7. Util-Vserver is 0.30.211 (debian compiled). The vservers' partition is a XFS-filesystem mounted with the tagxid-option. as there seems some xfs boom recently, and folks start to actually use that filesystem, I'm inclined to add the missing feature, given that there are a few folks willing to test that ... so please let me know if you're interested ... Sure, if you are willing to implement this feature I can do some tests, with the limitation that I only have a amd64 system at hand for testing. If this is ok, I just need to know what to do ...:-) TIA, Herbert best regards, Alexander Thanks in advance, Alexander -- netzwerk- systemadministrator --- agoeres at lieblinx. net tel.: +49 (0)30 / 62 90 81 05 fax: +49 (0)30 / 69 00 46 03 --- lieblinx we do software --- reichenberger straße 125 10999 berlin http://lieblinx.net --- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] a question regarding disk limits
Hello List! I'm trying to make the disk-limits work for my vservers to gain some flexibility and ran into a problem: the disk limits seem to be disfunctional. I wonder if anyone could help me with that .. I followed the instructions provided on http://oldwiki.linux-vserver.org/Disk+Limits: - created a directory /etc/vservers/test1/dlimit/0 - in there I created the files space_total with 716800, inode_total with 10, reserved with 5 and directory with /var/lib/vservers/test - I was tagging the files in /var/lib/vservers: chxid -r --xid /var/lib/vservers/test When I reduced the space_total to an amount smaller than the actual vserver content vserver test start refused to come up, complaining that there is not enough space. After adjusting the space, the vserver could be started. Doing a df -kh inside the vserver gave: FilesystemSize Used Avail Use% Mounted on /dev/hdv1 700M 579M 87M 88% / Until here everything looks fine. The error showed, when inside this vserver I succeed doing a: dd if=/dev/zero of=testfile bs=1M count=1024 This produced a 1 GB big file inside the vserver that claimed to have only 87 MB left. Are the disk limits functional? If yes, how are they to be set up? Any advice is appreciated. The vserver-version is a vanilla kernel 2.6.19.2 with vs 2.2.0-rc7. Util-Vserver is 0.30.211 (debian compiled). The vservers' partition is a XFS-filesystem mounted with the tagxid-option. Thanks in advance, Alexander -- netzwerk- systemadministrator --- agoeres at lieblinx. net tel.: +49 (0)30 / 62 90 81 05 fax: +49 (0)30 / 69 00 46 03 --- lieblinx we do software --- reichenberger straße 125 10999 berlin http://lieblinx.net --- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Re: future vserver on ubuntu
Nice to know, thanks for the info... cheers, Alexander Am Dienstag, 28. November 2006 17:28 schrieb Peter Mann: On Tue, Nov 28, 2006 at 05:11:32PM +0100, alexander goeres - lieblinx GmbH wrote: just one question aside: is anybody able to figure out, what vserver-versions the debian-kernel-packagers are using? http://packages.debian.org/linux-image-vserver-686 http://packages.debian.org/linux-image-vserver-k7 http://packages.debian.org/changelogs/pool/main/l/linux-2.6/linux-2.6_2.6.1 7-9/changelog * Update vserver patch to 2.0.2. http://packages.debian.org/changelogs/pool/main/l/linux-2.6/linux-2.6_2.6.1 8-5/changelog * Update vserver patch to 2.0.2.2-rc6. -- netzwerk- systemadministrator --- agoeres at lieblinx. net tel.: +49 (0)30 / 61 20 26 86 fax: +49 (0)30 / 69 00 46 03 --- lieblinx we do software --- reichenberger straße 125 10999 berlin http://lieblinx.net --- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] some questions about debian-vserver
Am Freitag, 28. April 2006 06:45 schrieb Peter Mann: On Fri, Apr 28, 2006 at 06:37:19AM +0200, Peter Mann wrote: On Thu, Apr 27, 2006 at 10:38:23AM +0200, alexander goeres - lieblinx.net wrote: vserver-kernels. But my last experience with the debian-util-vserver tools stands strictly against it. So I'd like to know if anyone here has already gathered experience with these debian kernels? Do they work? Better than debian util-vserver? Are there any flaws included beyond normal vservers? Package: vserver-debiantools Package: util-vserver oh, i forgot question: what's wrong with the debian-util-vserver ... what exactly is debian-util-vserver ??? vserver-debiantools ??? Some weeks ago i accidentally installed the debian package of util-vserver 0.30.210 on one of our machines, thus destroying the setup of a well working vserver host: nothing vserver-related was working anymore. It took me one day to get rid of it (I finally did a fresh setup of the host). Herbert posted a solution for this problem here on the list later. So I've become cautious regarding the debian implementations of anything vserver related. Alexander -- netzwerk- systemadministrator --- agoeres at lieblinx. net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 69 00 46 03 --- lieblinx.net we do software --- reichenberger straße 125 10999 berlin http://lieblinx.net --- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] some questions about debian-vserver
Hello List, I recently found a debian kernel package (in unstable) that claims to have the vserver-patch already included. Somwhere in the changelog the maintainers say, it's a vserver patch to 2.0.2-rc17. Since I'd prefer to use well built packages, constructed by experts, instead of my selfmade faulty kernel-packages I think about using these vserver-kernels. But my last experience with the debian-util-vserver tools stands strictly against it. So I'd like to know if anyone here has already gathered experience with these debian kernels? Do they work? Better than debian util-vserver? Are there any flaws included beyond normal vservers? If anybody has any user stories regarding these debian-vserver-kernels, could you share your experience with them? Thanks in advance Alexander -- netzwerk- systemadministrator --- agoeres at lieblinx. net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 69 00 46 03 --- lieblinx.net we do software --- reichenberger straße 125 10999 berlin http://lieblinx.net --- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] testme.sh error and vserver does not start
Hi List, I ran into a similar problem. I tried to update a vserver host running debian by using the debian-package and installed their util-vserver (0.30.210-2) from unstable. Then the Vservers (that were running before) refused to start. I uninstalled the debian util-vserver package and installed a self-compiled 0.30.210 that works well on many other hosts. Unluckily now it refuses to do so. testme.sh gives me this: - Linux-VServer Test [V0.15] Copyright (C) 2003-2006 H.Poetzl vcontext: execvp(grep): Permission denied chcontext failed! chbind is working. Linux 2.6.15.3-vs2.0.1.2-nosmp #1 Thu Feb 16 17:48:17 CET 2006 x86_64 Ea 0.30.210 236/glibc (DSa) compat,v11,v13,net,oldproc,olduts VCI: 0002:0001 236 0376 (TbLgnP) --- I had let run /etc/init.d/vprocunhide it tells me, the proc-security-entries are fixed. This kernel and these self-compiled utils run well on other hosts and i never tried to use the debian utils before (and most certainly never will again) Could anybody here help me to get my vservers running again? Thanx in advanc Alexander Am Mittwoch, 5. April 2006 09:49 schrieb Laurent CARON: Hi, It seems something is wrong on my setup, but i dont know exactly what :$ ./testme.sh Linux-VServer Test [V0.15] Copyright (C) 2003-2006 H.Poetzl vcontext: execvp(grep): No such file or directory chcontext failed! chbind is working. Linux 2.6.16-vs2.1.1-rc13-vs-20060405 #1 SMP PREEMPT Wed Apr 5 09:04:35 CEST 2006 i686 Ea 0.30.210 273/glibc (DSa) v13,net VCI: 0002:0001 273 03000116 (TbLgnP) It seems something is missing, broken:$ vserver vs-master start access(/proc/uptime): Permission denied /proc/uptime can not be accessed. Usually, this is caused by procfs-security. Please read the FAQ for more details http://www.linux-vserver.org/index.php?page=Linux-Vserver+FAQ Failed to start vserver 'vs-master' I looked in the FAQs provided at this url, but i didn't find what causes this problem. Thanks Laurent ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver -- netzwerk- systemadministrator --- agoeres at lieblinx. net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 69 00 46 03 --- lieblinx.net we do software --- reichenberger straße 125 10999 berlin http://lieblinx.net --- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] mountpoints blocked - reloaded -- any updates ?
Hello List, hello Herbert, is there any update or solution regarding this problem? regards, Alexander Am Samstag, 18. Februar 2006 00:38 schrieb Herbert Poetzl: On Fri, Feb 17, 2006 at 01:50:41PM +0100, Oliver Welter wrote: Hi Folks, Hi Bertl, the problem which seemed to be solved re-appeard today with recent kernel patches (2.6.15-gentoo-r4-vs2.1.1-rc6) To reconstruct the problem 1) add a drbd blockdevice to the guests fstab 2) start and stop guest 3) try to unmount the device you get an error, telling that the drbd device is still mounted... So - any ideas ?? okay, just as update, we tracked this down to the fact that even mainline 2.6.15/2.6.16-rc3 does not release ext3 filesystems properly when the namespace is destroyed ... this can be easily verified with a mainline kernel and the following command sequence: vnamespace --new -- mount /dev/hda1 /mnt (assuming that /dev/hda1 contains an ext3 fs and /mnt exists, this will claim hda1 but not release it -- it works fine with ext2 though) now investigating ... best, Herbert I am sure that there are no other contexts running, the maschine was booted freshly before doing the above steps and the testsystem was the only running guest Oliver -- --==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-- Dipl.-Ing. Oliver Welter - microBLUE - http://www.microblue.de Tel: 08131/80525 - Fax: 08131/80526 - Post: Loestr. 15; 85221 Dachau webbasierte Anwendungen - Servertechnik - Groupware - PCs und Netzwerke --==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-- ___ 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] problems starting and stopping a vserver
Hello Herbert, Thanx for the quick reply. Am Donnerstag, 2. März 2006 16:08 schrieb Herbert Poetzl: On Thu, Mar 02, 2006 at 03:39:09PM +0100, alexander goeres - lieblinx.net wrote: Hello List , I recently set up a new machine with Version 2.0.1 of the vservers and 0.30.210 of the util-vserver. It's a vanilla kernel 2.6.15-3 on a debian host on a AMD 64 3200+. There I discovered some problems with the startup of services inside the vservers (debian guests). Zope instances that are started through init-scripts fail and die after some time without any further notice. might be interesting to add an 'strace -fF -o zope.trace ...' to the relevant section of the startup script (the zope script) so that we might get an idea what happens and why it fails I followed your advice and got about 18MB of logfile for the start procedure during vserver startup and about 6Mb during a start from within a vserver. Well, now I'm trying to pin down an inhouse programmer to explain that to me .. :-/ Starting them after the init-procedure works as it should. I fear that this is mainly zope-related but it can't be only a mistake with zope since it was working perfectly on older vserver-versions. do they stay 'forever' then, or do they fail/die after some time too, when started _after_ the init procedure? Starting zope with the init-script after the vserver-startup makes the instances permanent, just as it should. If anybody here had run into a similar problem and had solved it I'd gladly accept any hints to the solution. are you sure that the 'only' thing you changed was the kernel and util-vserver? maybe a distro update too? maybe a new hardware? I was mistaken to claim that the zope-startup through init-scripts worked on previous vserver versions. I checked all our hosts and found that it had _never_ worked on the hosts with vserver 1.9.x to 2.0.1. I just never had the idea to test that, assuming that of course it would be functional and since I never had to restart the vservers I failed to notice this. So I guess it's rather really a zope problem. I put that in the back to investigate it later. So there's only my problems with using fakeinit left. Trying to solve this I started the relevant vservers with the fakeinit-flag and the plain initstyle. Now the start of the vserver's init scripts is normal but stopping the vserver fails with the notice: host:/etc/vservers# vserver testserver stop A timeout occured while waiting for the vserver to finish and it will be killed by sending a SIGKILL signal. The following process list might be useful for finding out the reason of this behavior: -- 12105 120 testserver?SNs0:00 init [2] 12254 120 testserver?SNs0:00 /sbin/syslogd 12261 120 testserver?SNs0:00 /usr/lib/exim/exim3 -bd -q30m 12266 120 testserver?SNs0:00 /usr/sbin/inetd 12273 120 testserver?SNs0:00 /usr/sbin/sshd 12276 120 testserver?SNs0:00 /usr/sbin/atd 12279 120 testserver?SNs0:00 /usr/sbin/cron -- Sometimes this list is empty. that's not too unusual, and you might fix that in the shutdown script by killing off all kind of stuff inside the guest, which just seems not to be done atm ... Starting and stopping the vservers with the sysv initstyle and without the fakeinit flag shows that the services are started and stopped as intended. All services are started though, when starting a vserver with the fakeinit flag. Why should the shutdown procedure fail? Is there anything to be changed within the vservers when switching to plain initstyle and using the fakeinit flag? The vservers themselves are all debian guests. I'd be glad if anybody had an idea how to debug this: either start the services nomally at vserver-startup (preferred) or getting rid of this fakeinit-stop problem. HTH, Herbert Regards, Alexander -- netzwerk- systemadministrator --- agoeres at lieblinx. net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 69 00 46 03 --- lieblinx.net we do software --- reichenberger straße 125 10999 berlin http://lieblinx.net --- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] problems starting and stopping a vserver: partially solved
Hello Herbert, I found my error with the zope-start at vserver-startup: it was a missing PATH in the vserver's init script for zope. I'm sorry to having bothered the list and you with that.. That doesn't exactly solve my other problems regarding the unclean shutdowns of a vserver that was started with the fakeinit-flag. But it changes them more or less to purley academic problems, since I don't need this fakeinit stuff now no more. best regards, Alexander Am Freitag, 3. März 2006 13:12 schrieb alexander goeres - lieblinx.net: Hello Herbert, Thanx for the quick reply. Am Donnerstag, 2. März 2006 16:08 schrieb Herbert Poetzl: On Thu, Mar 02, 2006 at 03:39:09PM +0100, alexander goeres - lieblinx.net wrote: Hello List, I recently set up a new machine with Version 2.0.1 of the vservers and 0.30.210 of the util-vserver. It's a vanilla kernel 2.6.15-3 on a debian host on a AMD 64 3200+. There I discovered some problems with the startup of services inside the vservers (debian guests). Zope instances that are started through init-scripts fail and die after some time without any further notice. might be interesting to add an 'strace -fF -o zope.trace ...' to the relevant section of the startup script (the zope script) so that we might get an idea what happens and why it fails I followed your advice and got about 18MB of logfile for the start procedure during vserver startup and about 6Mb during a start from within a vserver. Well, now I'm trying to pin down an inhouse programmer to explain that to me .. :-/ Starting them after the init-procedure works as it should. I fear that this is mainly zope-related but it can't be only a mistake with zope since it was working perfectly on older vserver-versions. do they stay 'forever' then, or do they fail/die after some time too, when started _after_ the init procedure? Starting zope with the init-script after the vserver-startup makes the instances permanent, just as it should. If anybody here had run into a similar problem and had solved it I'd gladly accept any hints to the solution. are you sure that the 'only' thing you changed was the kernel and util-vserver? maybe a distro update too? maybe a new hardware? I was mistaken to claim that the zope-startup through init-scripts worked on previous vserver versions. I checked all our hosts and found that it had _never_ worked on the hosts with vserver 1.9.x to 2.0.1. I just never had the idea to test that, assuming that of course it would be functional and since I never had to restart the vservers I failed to notice this. So I guess it's rather really a zope problem. I put that in the back to investigate it later. So there's only my problems with using fakeinit left. Trying to solve this I started the relevant vservers with the fakeinit-flag and the plain initstyle. Now the start of the vserver's init scripts is normal but stopping the vserver fails with the notice: host:/etc/vservers# vserver testserver stop A timeout occured while waiting for the vserver to finish and it will be killed by sending a SIGKILL signal. The following process list might be useful for finding out the reason of this behavior: -- 12105 120 testserver?SNs0:00 init [2] 12254 120 testserver?SNs0:00 /sbin/syslogd 12261 120 testserver?SNs0:00 /usr/lib/exim/exim3 -bd -q30m 12266 120 testserver?SNs0:00 /usr/sbin/inetd 12273 120 testserver?SNs0:00 /usr/sbin/sshd 12276 120 testserver?SNs0:00 /usr/sbin/atd 12279 120 testserver?SNs0:00 /usr/sbin/cron -- Sometimes this list is empty. that's not too unusual, and you might fix that in the shutdown script by killing off all kind of stuff inside the guest, which just seems not to be done atm ... Starting and stopping the vservers with the sysv initstyle and without the fakeinit flag shows that the services are started and stopped as intended. All services are started though, when starting a vserver with the fakeinit flag. Why should the shutdown procedure fail? Is there anything to be changed within the vservers when switching to plain initstyle and using the fakeinit flag? The vservers themselves are all debian guests. I'd be glad if anybody had an idea how to debug this: either start the services nomally at vserver-startup (preferred) or getting rid of this fakeinit-stop problem. HTH, Herbert Regards, Alexander -- netzwerk- systemadministrator --- agoeres at lieblinx. net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 69 00 46 03 --- lieblinx.net we do software
[Vserver] problems starting and stopping a vserver
Hello List , I recently set up a new machine with Version 2.0.1 of the vservers and 0.30.210 of the util-vserver. It's a vanilla kernel 2.6.15-3 on a debian host on a AMD 64 3200+. There I discovered some problems with the startup of services inside the vservers (debian guests). Zope instances that are started through init-scripts fail and die after some time without any further notice. Starting them after the init-procedure works as it should. I fear that this is mainly zope-related but it can't be only a mistake with zope since it was working perfectly on older vserver-versions. If anybody here had run into a similar problem and had solved it I'd gladly accept any hints to the solution. Trying to solve this I started the relevant vservers with the fakeinit-flag and the plain initstyle. Now the start of the vserver's init scripts is normal but stopping the vserver fails with the notice: host:/etc/vservers# vserver testserver stop A timeout occured while waiting for the vserver to finish and it will be killed by sending a SIGKILL signal. The following process list might be useful for finding out the reason of this behavior: -- 12105 120 testserver?SNs0:00 init [2] 12254 120 testserver?SNs0:00 /sbin/syslogd 12261 120 testserver?SNs0:00 /usr/lib/exim/exim3 -bd -q30m 12266 120 testserver?SNs0:00 /usr/sbin/inetd 12273 120 testserver?SNs0:00 /usr/sbin/sshd 12276 120 testserver?SNs0:00 /usr/sbin/atd 12279 120 testserver?SNs0:00 /usr/sbin/cron -- Sometimes this list is empty. I'd be glad if anybody had an idea how to debug this: either start the services nomally at vserver-startup (preferred) or getting rid of this fakeinit-stop problem. Everything worked normally on older (might be ancient for the developers) vserver versions, eg. vs1.9.5 on a vanilla 2.6.8 kernel with util-vserver 0.30.207. Here's the output of vserver-info for the problematic host. Versions: Kernel: 2.6.15.3-vs2.0.1.2-nosmp VS-API: 0x00020001 util-vserver: 0.30.210; Feb 28 2006, 11:06:46 Features: CC: x86_64-linux-gcc, x86_64-linux-gcc (GCC) 3.3.5 (Debian 1:3.3.5-13) CXX: x86_64-linux-g++, x86_64-linux-g++ (GCC) 3.3.5 (Debian 1:3.3.5-13) CPPFLAGS: '' CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W' CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W -fmessage-length=0' build/host: x86_64-pc-linux-gnu/x86_64-pc-linux-gnu Use dietlibc: yes Build C++ programs: yes Build C99 programs: yes Available APIs: v13,net ext2fs Source: e2fsprogs syscall(2) invocation: alternative vserver(2) syscall#: 236/glibc Paths: prefix: /usr sysconf-Directory: /etc cfg-Directory: /etc/vservers initrd-Directory: $(sysconfdir)/init.d pkgstate-Directory: /var/run/vservers vserver-Rootdir: /vservers Thanx in advance Alexander Goeres -- netzwerk- systemadministrator --- agoeres at lieblinx. net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 69 00 46 03 --- lieblinx.net we do software --- reichenberger straße 125 10999 berlin http://lieblinx.net --- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] some confusions about cache an vdlimit
Hello List! I'm trying to set up a new host with the actual state-of-the-arrt (stable , of course :-) vserver-version 2.01. I got a vanilla kernel 2.6.15.3 applied the patches and everything is nice up to now. I even succeeded in compiling and installing the util-vserver-0.30.210 tools Great! But then i ran into some problems, that confused me beyond normal: What is the purpose of this cache-directory, that shows up in the horrible flower page ? Is it necessary? When I tried to remember the usage of vdlimit typing vdlimit --help gave this: vdlimit --xid xid [--flags flags] (--set limit=value|--remove) mount point But previous versions of vdlimit were to be applied to a directory on the file system (that was mounted with the tagxid option) not to a mount point. Did this change back to pre-vdlimit-style? I anybody could help me with this? Thanx in advance Alexander Goeres -- netzwerk- systemadministrator --- agoeres at lieblinx. net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 69 00 46 03 --- lieblinx.net we do software --- reichenberger straße 125 10999 berlin http://lieblinx.net --- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Re: Strange error when stopping a vserver
Solved it, but can't say if this is a good or bad solution: The message disappears, when the vshelper application is disabled. Greetings Alexander Am Mittwoch, 16. November 2005 11:51 schrieb Nicolas Costes: Le Mardi 15 Novembre 2005 18:31, Herbert Poetzl a écrit : On Tue, Nov 15, 2005 at 11:06:06AM +0100, alexander goeres - lieblinx.net wrote: I recently set up a new host for another set of vservers and something seems to be wrong, but I can't find a solution. When doing a vsever xyz stop the relevant vserver stops, but shows this msg. looks like the stop script is killed ... my suggestion: try the mainstream 0.30.209, if the issue remains, we will investigate further ... I posted this as a bug a few weeks ago : http://savannah.nongnu.org/bugs/?func=detailitemitem_id=14592 Like Herbert said, 0.30.209 may correct this; at least Enrico seems to have added stuff to debug this... -- netzwerk- systemadministrator --- agoeres at lieblinx. net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 69 00 46 03 --- lieblinx.net we do software --- reichenberger straße 125 10999 berlin http://lieblinx.net --- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Strange error when stopping a vserver
Hello everybody,
I recently set up a new host for another set of vservers and something seems
to be wrong, but I can't find a solution. When doing a vsever xyz stop the
relevant vserver stops, but shows this msg.
/usr/sbin/vserver: line 85: 27923 killed [EMAIL PROTECTED]
${USE_VNAMESPACE:+$_VNAMESPACE --enter $S_CONTEXT -- } $_VCONTEXT $SILENT
_OPT --migrate --chroot --xid $S_CONTEXT -- [EMAIL PROTECTED]
The vserver is stopped though, but the mentioned line 85 of /usr/sbin/vserver
doesn't show anything I could relate to this message. I also couldn't find
anything here on the list about that ...
I'd like to get rid of this or even better, solve this problem and would be
glad for any help.
I'm using the debian vserver-patches 2.0 on a debian kernel 2.6.12. The
util-vservers are the debian-stuff (0.30.208)
thanks in advance
Alexander Goeres
---
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Vservers under Debian
The problem with /proc inside a vserver looks as if you might have forgotten to unhide the proc entries. Compiling util-vservers from source and installing them gave an /etc/init.d/vprocunhide script on the main server, that solved the problem for me Have success. Alexander Am Donnerstag, 31. März 2005 18:16 schrieb Gaz Wilson: Does anyone have any experience with the development branch of Vserver and Debian? I'm having trouble with things not running within the vserver, most notably w and ifconfig, although my testing stopped there, there may be many more... I have a totally clean build of Debian (Sarge), running kernel 2.6.11 and VS 1.9.5 built from source. I have built util-vserver-0.30.204 from source, with the following configure line: ./configure --with-vrootdir=/local/vservers Which went well, this was installed. I have then created a vserver with the following command line: vserver test01 build -m debootstrap --hostname test01 --netdev eth0 --interface 172.29.31.242/16 -- -d sarge Which appeared to go well. I then started it up: host01:/# vserver test01 start Starting system log daemon: syslogd. Starting kernel log daemon: klogd. Starting MTA: exim4. Starting internet superserver: inetd. Starting deferred execution scheduler: atd. Starting periodic command scheduler: cron. All OK so far, but when I enter the server, I get all sorts of oddness... If I enter the vserver, then execute in this order: ls, mount, df, w, ifconfig, ifconfig -a, mount /proc and id - I get: host01:/# vserver test01 enter mesg: /dev/pts/0: Operation not permitted test01:/# ls bin dev homelibmnt proc sbin sys usr boot etc initrd media opt root srv tmp var test01:/# mount /dev/hdv1 on / type ufs (defaults) none on /proc type proc (defaults) none on /tmp type tmpfs (size=16m,mode=1777) none on /dev/pts type devpts (gid=5,mode=620) test01:/# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/hdv1 63457000176252 60057308 1% / none 16384 0 16384 0% /tmp test01:/# w Error: /proc must be mounted To mount /proc at boot you need an /etc/fstab line like: /proc /proc procdefaults In the meantime, mount /proc /proc -t proc test01:/# ifconfig Segmentation fault test01:/# ifconfig -a Segmentation fault test01:/# mount /proc mount: permission denied test01:/# id uid=0(root) gid=0(root) groups=0(root) I have read many many pages of documentation from various servers including: http://lena.franken.de/linux/debian_and_vserver/vserver.html http://linux-vserver.org/alpha+util-vserver http://www.13thfloor.at/vserver/* http://www.solucorp.qc.ca/miscprj/s_context.hc etc etc but to no avail. Has anyone seen this issue before and can they advise me what might be astray? I guess there could be something in the kernel that is missing or needed, but I couldn't say... GW -- netzwerk- systemadministrator --- agoeres at lieblinx. net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 69 00 46 03 --- lieblinxNET we do software a marwood thiele GbR --- reichenberger straße 125 10999 berlin http://lieblinx.net --- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Debian vserver guest
Am Mittwoch, 9. März 2005 22:29 schrieb Gilles: Hello. [...] 4. Network interfaces (a) In the /etc/init.d/reboot script: Remove the -i option (to avoid the guest trying to deconfigure the network interfaces upon halting). Great hint! I just coudn't find the part of the start/stop scripts that always tried to shut down eth0. (b) At vserver template stop, the following error is printed: Rebooting... /usr/local/util-vserver/sbin/vserver: line 740: test: too many arguments but there are only 273 lines in that file! In february Oliver Heinz had realized this in a mail here: vserver stop gives me an error: ++ test -n 0 -ne 0 /usr/local/sbin/vserver: line 740: test: too many arguments ... which comes from vserver.functions: elif test -n [EMAIL PROTECTED] -ne 0; then Is there just the first -n too much?! That worked for me! Have success Alexander Goeres -- netzwerk- systemadministrator --- agoeres at lieblinx. net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 69 00 46 03 --- lieblinxNET we do software a marwood thiele GbR --- reichenberger straße 125 10999 berlin http://lieblinx.net --- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] stale vserver run files
Hello list! I'm trying to get into the 1.9.x-future branch of vservers and (not unexpectedly) ran into some problems. My setup is with Debian as host and vserver system, vanilla kernel 2.6.10 and the 1.9.4 vserver patch. I plan to set up a master-vserver, configured and ready to be copied whenever a real vserver is needed. I already had such a constellation set up with the old-style-vservers and that worked perfectly. My master-vserver is running fine using fakeinit and the plain init style. Copying it to a real vserver is working too. On problem comes up, when I stop the copied vserver. Stopping it ends up with the errormsg Vserver '/etc/vservers/beta' still running unexpectedly; please investigate it manually... I did as advised and found that it's only pretending to be running still because a vserver beta status gives: Vserver 'beta' is stopped. It looks as if only the run-file /var/run/vservers/beta would still exist. This doesn't sound too serious but I'd like to know if anybody could point me to a solution of how to make it work correctly. The master-vserver alfa nicely removes its run file. Greetings Alexander -- netzwerk- systemadministrator --- agoeres at lieblinx. net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 69 00 46 03 --- lieblinxNET we do software a marwood thiele GbR --- reichenberger straße 125 10999 berlin http://lieblinx.net --- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] fakeinit flag, fixed context id and disk limits
Hi Herbert, Am Freitag, 28. Mai 2004 11:51 schrieb Herbert Poetzl: Only thing I found was Herbert mentioning it would work in the 1.3x branch but perhaps that changed in the meantime?? interesting that I should have mentioned that explicitely, but I can assure you, that this hasn't changed ... Just to make sure, that I'm not hallucinating informations..:-) from one mail of yours on 18.01.04: has been quite some time, right? That's obviously ages in develspace, but not too long in userspace. ... here some (currently valid) facts: - 1.27 is the latest stable release - 0.29.5 are the suggested util-vserver tools - fakeinit _with_ static contexts work for that as written in that mail, you can try with the testme.sh This version 0.29.5 ... is it the same as the version util-vserver 0.29 that is mentioned in the News on http://linux-vserver.org or rather some version from the util-vserver alpha branch I didn't find? rgrds, Alexander -- Netzwerk- Systemadministrator --- agoeres _at_ lieblinx.net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 61 20 26 89 --- lieblinxNET we do software a Marwood Thiele GbR --- reichenberger straße 125 10999 Berlin http://lieblinx.net --- ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] fakeinit flag, fixed context id and disk limits
Am Freitag, 28. Mai 2004 13:13 schrieb Bjoern Steinbrink: On Fr, 2004-05-28 at 13:06, Alexander Goeres wrote: ... here some (currently valid) facts: - 1.27 is the latest stable release - 0.29.5 are the suggested util-vserver tools - fakeinit _with_ static contexts work for that as written in that mail, you can try with the testme.sh This version 0.29.5 ... is it the same as the version util-vserver 0.29 that is mentioned in the News on http://linux-vserver.org or rather some version from the util-vserver alpha branch I didn't find? The numbering scheme for util-vserver is found here: http://www.linux-vserver.org/index.php?page=alpha+util-vserver so 0.29.5 is a devel release of the stable branch (as is 0.29.4 which is mentioned on the page for the linux-vserver 1.27 stable release) HTH Bjrn Been there and finally found it, thanks for the info Alexander -- Netzwerk- Systemadministrator --- agoeres _at_ lieblinx.net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 61 20 26 89 --- lieblinxNET we do software a Marwood Thiele GbR --- reichenberger strae 125 10999 Berlin http://lieblinx.net --- ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] fakeinit flag, fixed context id and disk limits
Hello to everybody and especially to Herbert.. Just one question, because I couldn't find anything about it in my mails from the list: Can the fakeinit flag be applied with static context ids and the setting of disk limits in the stable vserver branch? Only thing I found was Herbert mentioning it would work in the 1.3x branch but perhaps that changed in the meantime?? Thanx in advance Alexander -- Netzwerk- Systemadministrator --- agoeres \at lieblinx . net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 61 20 26 89 --- lieblinxNET we do software a Marwood Thiele GbR --- reichenberger straße 125 10999 Berlin http://lieblinx.net --- ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] [Release] Context Quota Disk Limits q0.13
Am Dienstag, 10. Februar 2004 15:28 schrieb Herbert Poetzl: if there is demand, a release for the stable branch will follow (just let me know) enjoy, Herbert Hi Herbert! Yes, there is! rgds Alexander -- --- agoeres _at_ lieblinx.net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 61 20 26 89 --- lieblinxNET we do software a Marwood Thiele GbR --- reichenberger straße 125 10999 Berlin http://lieblinx.net --- ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] [Release] vs1.00, vs1.22 and vs1.3.3 for 2.4.24
Hi Chistian! Thanks a lot, merci beaucoup, vielen Dank, mange tak!! It really works! Looks as if it's nessesary to read the kernel-source-docs even if one never intends to become a kernel hacker.. So bashing foreign admins is no longer needed, what a relief..:-) Greetings Alexander Am Mittwoch, 7. Januar 2004 18:50 schrieb Christian Mayrhuber: christian niessner wrote: das ist aber nicht zufaellig das tcp_ecn problem? cat /proc/sys/net/ipv4/tcp_ecn echo 0 /proc/sys/net/ipv4/tcp_ecn weil, imho, bis 2.4.18 war default 0, ab 2.4.19 ist default 1... ciao, marvin Ja ist es! (Yes it is!) Vielen Dank! Here is what /usr/src/linux/Documentation/Configure.help says about it: TCP Explicit Congestion Notification support CONFIG_INET_ECN Explicit Congestion Notification (ECN) allows routers to notify clients about network congestion, resulting in fewer dropped packets and increased network performance. This option adds ECN support to the Linux kernel, as well as a sysctl (/proc/sys/net/ipv4/tcp_ecn) which allows ECN support to be disabled at runtime. Note that, on the Internet, there are many broken firewalls which refuse connections from ECN-enabled machines, and it may be a while before these firewalls are fixed. Until then, to access a site behind such a firewall (some of which are major sites, at the time of this writing) you will have to disable this option, either by saying N now or by using the sysctl. If in doubt, say N. An enty in /etc/sysctl.conf: net/ipv4/tcp_ecn=0 and systcl -p will do away with this problem. -- --- agoeres _at_ lieblinx.net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 61 20 26 89 --- lieblinxNET we do software a Marwood Thiele GbR --- reichenberger straße 125 10999 Berlin http://lieblinx.net --- ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] [Release] vs1.00, vs1.22 and vs1.3.3 for 2.4.24
For my problem, I don't think it's vserver-related. Today I could compile a vanilla 2.4.23-kernel on the relevant host-server without any vserver implementation. After a reboot in this kernel I did a telnet remote.mail.server 25 from the host-server and it timed out as before. It looks as if it's a firewall-problem on the remote side but the admins in charge there of course claim, that it's not so.. I can't look into their firewall, but a more agressive approach with 1. nmap -p 25 -sS remote.mail.server and 2. nmap -p 25 -sA remote.mail.server from one of my host-servers showed for 1.: port 25 open and for 2.:port 25 filtered. That sounds exactly like your explanation. But for my host-servers it occurs no matter if they have a vserver-patched kernel running or not. Too bad, for a short time I thought I might have tracked this problem down and could accuse Herbert and the developers here of doing bad work instead of fighting alien admins.. :-) greetings Alexander Am Mittwoch, 7. Januar 2004 13:41 schrieb Christian Mayrhuber: Christian Mayrhuber wrote: Thats exactly the problem I have. The dns setup is right. It happens from the root server (ctx 0), too. But does not happen if I use a standard kernel with the same configuration. The remote mailserver is behind a netfilter firewall. Some additional information: The remote mailserver is behind a netfilter firewall and complains about an invalid CRC in the TCP header, the CRC of the IP header is ok. The CRC of the TCP header is ok when the packets are sent from a vserver (this has been verified on a pix firewall) then those packets get routed trough the net, reach the netfilter firewall and have a corrupt TCP CRC afterwards. This may well be a bug in the netfilter code which is triggerd only by packets of a vserver kernel. The result is that on the SYN packet follows no ACK and the connection times out. -- --- agoeres _at_ lieblinx.net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 61 20 26 89 --- lieblinxNET we do software a Marwood Thiele GbR --- reichenberger straße 125 10999 Berlin http://lieblinx.net --- ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] [Release] vs1.00, vs1.22 and vs1.3.3 for 2.4.24
Hi Christian! Could you describe how this problem looked like? I have a mail-sending problem too and have absolutely no idea anymore, how to solve it: A mailserver running on a vserver on a 2.4.23-vs1.21-host can't contact one single remote mailserver (only 1 :-\). Connection always times out... and that's it. works well with all other mailservers. A telnet to port 25 from the host itself to this single mailserver times out equally.. could this be a vserver-related problem? I'd never thought of that.. Greetings Alexander Am Dienstag, 6. Januar 2004 14:22 schrieb Christian Mayrhuber: The IPV4 bug is in vserver 1.00, but fixed in vserver 1.22, right? Recently, I had problems to send mail to a machine behind a netfilter firewall from a machine with a vserver 1.00 kernel. The firewall did not complain about corrupted packets, but the smtp server behind the firewall did. This happened with a ctx17 kernel, too. Things worked fine with a standard kernel. -- --- agoeres _at_ lieblinx.net tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 61 20 26 89 --- lieblinxNET we do software a Marwood Thiele GbR --- reichenberger straße 125 10999 Berlin http://lieblinx.net --- ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] is there any getting started with vserver documentation anywhere?
I once tried to make the vservers run on a SuSE disto but after serveral weekends gave up. That's basically due to my lack of ability to compile a vanilla kernel on SuSE so that all the modules it has with its standard kernel work. We run vservers under Debian 3.0 (Woody) without any problems. The normal vservers (without setting disk-space limits and without setting the context number :-)) are simple: I started with the introduction by Jacques (in april, I think) and worked up my way through the other docs in mentioned http://linux-vserver.org. Astonishingly there's not really much to do to run vservers: patching, compiling and installing the kernel, getting the tools of choice (either from the Debian distro or Enrico's util-vserver), setting up a vserver, do a vserver xxx start and that's it... As a kernel I use whatever is currently regarded as stable (on the long running system 2.4.18, on the systems to-be-set-up 2.4.22) and where the developers provide a patch. I found it to be very stable, relatively easy to install and extremely useful! Alexander Am Mittwoch, 5. November 2003 05:31 schrieb ian douglas: Considering RedHat's recent press release about discontinuing the RedHat Linux line in favor of the more expensive enterprise version, I'd really like a few answers from others (only had one off-list reply) regarding which operating system is going to be my best bet since I'm going to have to convert my server to another Linux distro now. I'll be starting a whole new server to manage everything but curious, obviously, which distro people have had the most success with other than RedHat. Thanks for any help on that, as well as my other unanswered questions. -id I searched the site's documentation and found the multi-page this is what it's capable of documentation, but didn't see any offhand that answered the following questions. I sent them to Jacques, but I'd like to pose it to the list in general for the 1.0 release so I can get started on vserver in the coming weeks. --- Hi Jacques, I've been daydreaming about a vserver setup for my system. A few things that perhaps would be handy to have in the FAQ: - what OS works 'best'? Kernel version is obviously important, but it would be neat to see some sort of volunteered information from various users as to the OS and version of that OS, that they have the most success with - how does one get started? is it best to start with a totally fresh machine and build from there, or could I start from a medium-sized virtual hosting setup using Linuxconf and build a vserver and go from there? I guess I'm looking for guidance on what should/should not get copied over when building the first vserver - once I build the first one, I can just use the vserver software to duplicate it, but I'm worried about disk space and how to actually mount/share file system areas... - any patched versions of up2date out there? or would I have to tell up2date to save a copy of the RPM's on the disk somewhere and run the vserver rpm utility to patch all vservers? If I have 100 vservers, is there a quicker way to tell it to patch all vservers, or would I have to literally type rpm server1 server2 server3 ... server99 server100 -Uvh *rpm ? --- Thanks for any additional feedback. -id ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver -- --- [EMAIL PROTECTED] tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 61 20 26 89 --- lieblinxNET we do software a Marwood Thiele GbR --- reichenberger straße 125 10999 Berlin http://lieblinx.net --- ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Problems Setting Limits
Well, even 0.24 fails to compile under a kernel compiled with the patches from http://vserver.13thfloor.at/Linux2.6/index.php?page=Per+Context+Disk+Limits With the vserver-1.00 or c17f-patches everything works nicely, unluckily I'd like to test and use the ability to limit a vserver's space... Am Dienstag, 4. November 2003 00:24 schrieb Enrico Scholz: [EMAIL PROTECTED] (Alexander Goeres) writes: configure seems to run without problems, but make doesn't make it. ... gcc -DHAVE_CONFIG_H -I. -I. -I. -I ./lib -D VERSION=\0.23.96\ -D PKGLIBDIR=\/usr/local/lib/util-vserver\ -D _GNU_SOURCE -Wall -pedantic -g -O2 -Wall -pedantic -W -c -o src/capchroot.o `test -f 'src/capchroot.c' || echo './'`src/capchroot.c In file included from /usr/include/linux/fs.h:12, from linuxcaps.h:17, from src/capchroot.c:39: ... /usr/include/linux/radix-tree.h: In function `radix_tree_preload_end': Mmh, this looks like a heavily patched kernel. 'radix-tree.h' appears somewhere in kernel 2.5/2.6 and the kernel-headers were probably not updated completely. Recent version (0.23.98/0.24) should fix it by removing any #include's from linuxcaps.h. The previous messages are ok; util-vserver is C99 code which produces silly warnings with gcc-2.95. Enrico have fun Alexander --- [EMAIL PROTECTED] tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 61 20 26 89 --- lieblinxNET we do software a Marwood Thiele GbR --- reichenber straße 125 10999 Berlin http://lieblinx.net --- ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Problems Setting Limits
Hi Enrico! Am Samstag, 1. November 2003 00:08 schrieb Enrico Scholz: [EMAIL PROTECTED] (Alexander Goeres) writes: with util-vserver (which btw failed to compile completely Which errors, which environment? Build of 0.23.96 has been tested successfully on RH rawhide, RHL 7.3 and Debian 2.2. The environment is Debian 3.0 and a kernel that was patched with the patches from http://vserver.13thfloor.at/Linux2.6/index.php?page=Per+Context+Disk+Limits. configure seems to run without problems, but make doesn't make it. I'll attach the nohups of configure and make. greetings Alexander --- [EMAIL PROTECTED] tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 61 20 26 89 --- lieblinxNET we do software a Marwood Thiele GbR --- reichenber straße 125 10999 Berlin http://lieblinx.net --- X configure-output: checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for g++... g++ checking for C++ compiler default output... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for style of include used by make... GNU checking dependency style of g++... gcc checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... gcc checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for ranlib... ranlib checking whether gcc and cc understand -c and -o together... yes checking whether the C-compiler accepts -Werror -W... yes checking whether gcc accepts -std=c99... no checking whether gcc accepts -Wall... yes checking whether gcc accepts -pedantic... yes checking whether gcc accepts -W... yes checking whether gcc accepts -Wno-unused-parameter... no checking whether the C++-compiler accepts -Werror -W... yes checking whether g++ accepts -ansi... yes checking whether g++ accepts -Wall... yes checking whether g++ accepts -pedantic... yes checking whether g++ accepts -W... yes checking whether g++ accepts -fmessage-length=0... no checking for linux kernel dir... /lib/modules/2.4.22-c17e/build checking for linux kernel headers... /lib/modules/2.4.22-c17e/build/include checking which vserver-rootdir is to use... /var/lib/vservers checking for supported APIs... legacy,compat checking for sys_virtual_context... no checking whether MS_MOVE is declared... no checking for ctx_t... no configure: creating ./config.status config.status: creating util-vserver.spec config.status: creating Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands make output make[1]: Entering directory `/root/util-vserver-0.23.96' test -z sysv/rebootmgr sysv/v_gated sysv/v_httpd sysv/v_named sysv/v_portmap sysv/v_sendmail sysv/v_smb sysv/v_sshd sysv/v_xinetd sysv/vservers scripts/util-vserver-vars scripts/vkill scripts/vps linuxconf/newvserver linuxcaps.h linuxvirtual.h || rm -f sysv/rebootmgr sysv/v_gated sysv/v_httpd sysv/v_named sysv/v_portmap sysv/v_sendmail sysv/v_smb sysv/v_sshd sysv/v_xinetd sysv/vservers scripts/util-vserver-vars scripts/vkill scripts/vps linuxconf/newvserver linuxcaps.h linuxvirtual.h test -z lib/libvserver.a || rm -f lib/libvserver.a test -z tests/chrootsafe tests/escaperoot tests/forkbomb tests/testipc tests/testlimit tests/testopenf || rm -f tests/chrootsafe tests/escaperoot tests/forkbomb tests/testipc tests/testlimit tests/testopenf test -z src/capchroot src/fakerunlevel src/filetime src/ifspec src/listdevip src/parserpmdump src/readlink src/showattr src/showperm src/vbuild src/vcheck src/vreboot src/vunify || rm -f src/capchroot src/fakerunlevel src/filetime src/ifspec src/listdevip src/parserpmdump src/readlink src/showattr src/showperm src/vbuild src/vcheck src/vreboot src/vunify test -z src/chbind src/chcontext src/rebootmgr src/reducecap src/vdu src/vfiles src/vserver-stat || rm -f src/chbind src/chcontext src/rebootmgr src/reducecap src/vdu src/vfiles src/vserver-stat rm -f *.o core *.core rm -f lib/lib_libvserver_a-checkversion.o rm -f lib/lib_libvserver_a-getctx.o rm -f lib/lib_libvserver_a-getversion.o rm -f lib/lib_libvserver_a-syscall.o rm -f lib/lib_libvserver_a-uint2str.o rm -f src/capchroot.o rm -f src/chbind.o rm -f src/chcontext.o rm -f
