1104542703 N * Jinxi_ we2by 1104542711 M * we2by I can get a vds to start 1104542714 M * we2by :( 1104542727 M * we2by [root@localhost rc.d]# vserver t start 1104542727 M * we2by WARNING: can not find configuration, assuming legacy method 1104542727 M * we2by Starting the virtual server t 1104542727 M * we2by Error: /proc must be mounted 1104542727 M * we2by To mount /proc at boot you need an /etc/fstab line like: 1104542728 M * we2by /proc /proc proc defaults 1104542729 M * we2by In the meantime, mount /proc /proc -t proc 1104542731 M * we2by Failed to parse ps-output 1104542733 M * we2by Server t is not running 1104542735 M * we2by ipv4root is now 10.0.0.26 1104542737 M * we2by Host name is now localhost 1104542739 M * we2by Domain name is now 1104542741 M * we2by New security context is 50 1104542745 M * we2by capchroot: execvp("/etc/rc.d/rc"): No such file or directory 1104542748 M * we2by [root@localhost rc.d]# 1104542952 J * Jinxi_ ~Jinxi@dc5146d009.adsl.wanadoo.nl 1104542952 Q * we2by Read error: Connection reset by peer 1104546048 Q * sannes Read error: Connection reset by peer 1104553125 J * sannes ~ace@home.skarby.no 1104554304 N * Bertl_xX Bertl_zZ 1104554693 J * nox- ~nox@c135104.adsl.hansenet.de 1104555038 Q * nox Ping timeout: 480 seconds 1104555053 N * nox- nox 1104556085 Q * t____ Ping timeout: 480 seconds 1104559103 J * t____ ~tnichols@CPE-139-168-210-192.sa.bigpond.net.au 1104561061 Q * monrad Quit: Leaving 1104565850 Q * daniel_hozac oxygen.oftc.net orion.oftc.net 1104565893 J * daniel_hozac ~daniel@h212n1fls33o829.telia.com 1104575247 J * mboman ~michael@cm48.sigma230.maxonline.com.sg 1104578200 M * Jinxi_ Starting the virtual server t 1104578200 M * Jinxi_ Server t is not running 1104578200 M * Jinxi_ ipv4root is now 10.0.0.26 1104578200 M * Jinxi_ Host name is now localhost 1104578200 M * Jinxi_ Domain name is now 1104578202 M * Jinxi_ New security context is 50 1104578203 M * Jinxi_ capchroot: execvp("/etc/rc.d/rc"): No such file or directory 1104578212 M * Jinxi_ I get ride of the proc problem. but I still can start it 1104578255 M * _are_ new or old configuration? 1104578260 M * Jinxi_ new 1104578274 M * Jinxi_ [root@localhost scripts]# ./vprocunhide 1104578274 M * Jinxi_ [root@localhost scripts]# vserver t start 1104578295 M * _are_ k, does /etc/vserver/t/vdir/etc/rc.d/rc exist? 1104578356 M * Jinxi_ nope, it doesn 1104578401 M * Jinxi_ but my vservers are located in /vserver 1104578455 M * Jinxi_ [root@localhost vservers]# cd /vservers/t/etc/rc.d/ 1104578455 M * Jinxi_ [root@localhost rc.d]# pwd 1104578459 M * _are_ yes 1104578468 M * Jinxi_ [root@localhost rc.d]# ls 1104578468 M * Jinxi_ init.d rc rc0.d rc1.d rc2.d rc3.d rc4.d rc5.d rc6.d rc.local rc.sysinit 1104578471 N * Jinxi_ we2by 1104578492 M * _are_ but you need a link 'ln -s /vservers/t /etc/vserver/t/vdir' 1104578507 M * we2by ok 1104578571 M * _are_ vdir is basically a link to your chrooted environment, so you have everything in one place 1104578610 M * we2by k 1104578643 M * we2by ln -s /vservers/t/ /usr/local/etc/vserver/t/vdir 1104578643 M * we2by ln: creating symbolic link `/usr/local/etc/vserver/t/vdir' to `/vservers/t/': No such file or directory 1104578681 M * _are_ hmm, which part is missing? 1104578685 M * we2by done 1104578768 M * we2by failed 1104578769 M * we2by http://pastebin.com/189516 1104578849 M * we2by [root@localhost vdir]# ls /usr/local/etc/vservers/t/vdir 1104578849 M * we2by bin dev etc home lib proc root sbin tmp usr var 1104578851 M * _are_ obvious: save_ctxinfo: readlink("/usr/local/etc/vservers/t/run"): No such file or directory 1104578853 M * we2by is this correct? 1104578865 M * _are_ so you mis sthe 'run' liink as well. 1104578879 M * _are_ what is content ov your etc/vserver/t/ directory? 1104578884 M * _are_ there need a few links to be 1104578913 M * we2by [root@localhost vdir]# ls /usr/local/etc/vservers/t/ 1104578913 M * we2by vdir 1104578923 M * we2by what link do I need?? 1104578935 M * _are_ erm, you said you use 'new' configuration? 1104578955 M * _are_ looks more like 'no' configutration. ;) 1104578955 M * we2by I installed the new kernel 1104578960 M * we2by I installed the utilities 1104578971 M * we2by and this is my first time trying to get a vserver working 1104578982 M * _are_ ok, then I slowly get what happened 1104578997 M * we2by I wish there? a better doc 1104579012 M * _are_ hehe, yes 1104579032 M * we2by I hardly can get the kernel to compile 1104579035 M * we2by 2.6.10 1104579046 M * we2by anyway, so what should I do? what are the steps 1104579050 M * _are_ there is a page, quite unreadyble, but has the configuration tree: http://www-user.tu-chemnitz.de/~ensc/util-vserver/doc/conf/configuration.html 1104579069 M * we2by nice webpage 1104579070 M * we2by lol 1104579105 M * _are_ there are tools like 'vserver-build' that should do most of the stuff for you 1104579127 M * _are_ you have the server to be run already installed? 1104579186 M * we2by o bcapabilities this is a file? 1104579190 M * _are_ yes 1104579219 M * _are_ have here a vserver named 'samba': 1104579221 M * _are_ # ls -la /etc/vservers/samba/ 1104579222 M * _are_ total 40 1104579222 M * _are_ drwxr-xr-x 5 root root 4096 Dec 27 14:18 . 1104579222 M * _are_ drwxr-xr-x 21 root root 4096 Dec 29 18:22 .. 1104579222 M * _are_ drwxr-xr-x 3 root root 4096 Dec 21 14:09 apps 1104579222 M * _are_ -rw-r--r-- 1 root root 4 Dec 21 14:00 context 1104579222 M * _are_ -rw-r--r-- 1 root root 16 Dec 21 13:05 domainname 1104579224 M * _are_ -rw-r--r-- 1 root root 6 Dec 21 13:06 flags 1104579224 M * _are_ -rw-r--r-- 1 root root 112 Dec 22 13:13 fstab 1104579226 M * _are_ drwxr-xr-x 4 root root 4096 Dec 22 19:06 interfaces 1104579226 M * _are_ -rw-r--r-- 1 root root 77 Dec 21 13:59 interfaces.file 1104579228 M * _are_ lrwxrwxrwx 1 root root 27 Dec 27 12:22 run -> /usr/var/run/vservers/samba 1104579228 M * _are_ lrwxrwxrwx 1 root root 32 Dec 27 12:22 run.rev -> /etc/vservers/.defaults/run.rev/ 1104579230 M * _are_ drwxr-xr-x 2 root root 4096 Dec 21 13:58 uts 1104579230 M * _are_ lrwxrwxrwx 1 root root 15 Dec 27 12:22 vdir -> /vservers/samba 1104579248 M * _are_ it should look similar in your /usr/local/etc/vserver/t/ 1104579272 M * we2by seems like alot to do 1104579282 M * _are_ if you want to, I can tar up this directory and you can replace the names and see if it works 1104579306 M * we2by yea, great idea 1104579308 M * we2by lib/bcaps-v13.c 1104579314 M * we2by any idea where that file s? 1104579338 M * _are_ /usr/local/src/util-vserver-0.30.196/lib/bcaps-v13.c 1104579352 M * _are_ util-vserver source 1104579453 M * we2by great, I not a coder 1104579470 M * we2by I don have any idea how I can find out what I sould out in the file 1104579517 M * _are_ http://vgn.lihas.de/vservers-cfg-sample.tar.gz 1104579529 M * _are_ you need capability names? 1104579542 M * we2by if I have to 1104579607 M * _are_ # cat /etc/vservers/misc/bcapabilities 1104579607 M * _are_ NET_RAW 1104579619 M * _are_ just a file with one capability name per line 1104579656 M * we2by I need to change run and run.rev 1104579750 M * _are_ there are furter capabilities described: http://www.lids.org/lids-howto/node34.html 1104579757 M * _are_ yes 1104579809 M * _are_ I have a small script that copies some vserver to a new name and changes name and IP, not really advanced, but works for my purposes 1104579896 M * _are_ basically you need to change only run and vdir as links and alter the content of uts/nodename and context 1104579898 M * we2by the ip is the ip for the vserver? 1104579909 M * _are_ yes 1104580065 M * we2by should I change the fstab file? 1104580092 M * _are_ the fstab file *in* the vserver is completly useless 1104580131 M * _are_ the one in the vserver directory might help some stuff, but mostly for these management-filesystems like /proc /sys and /tmp 1104580132 M * we2by I almost done 1104580151 M * we2by only need to change the run and the run.rev links 1104580182 M * we2by where should I point run to? 1104580217 M * _are_ ln -s /usr/var/run/vservers/$dest /etc/vservers/$dest/run 1104580224 M * _are_ $dest is my new bserver name 1104580228 M * we2by run.rev is done 1104580234 M * _are_ it points into thin air with server not running 1104580268 M * _are_ hmpf, need to convince my webserver not to try and execute the kript I wanted to deposit there but displa yit. 1104580364 M * we2by I don have that /usr/var/run/vservers 1104580400 M * we2by should I make iT? 1104580486 M * _are_ well, this is the status directory you had with old vserver config, too 1104580556 M * _are_ if you had some t.ctx somewhere with old configuration, that is the directory 1104580564 M * _are_ it depends on your instalation 1104580583 M * we2by I don have any old config 1104580589 M * we2by should I leave it out 1104580752 M * _are_ you need it, but I can't tell you where it has to point to. 1104580762 M * _are_ you compile dthe tols yourself? 1104580767 M * we2by yep 1104580882 M * _are_ hmm, if I look a bit closer, probably it doesn't mater *where* the directory is 1104580916 M * _are_ so I'd probably make it /var/run/vservers 1104581067 M * we2by [root@localhost t]# vserver t start 1104581067 M * we2by mount: none already mounted or . busy 1104581067 M * we2by /usr/local/etc/vservers/t/fstab:1:1: failed to mount fstab-entry 1104581067 M * we2by mount: none already mounted or . busy 1104581067 M * we2by /usr/local/etc/vservers/t/fstab:3:1: failed to mount fstab-entry 1104581068 M * we2by vcontext: execvp("/etc/rc.d/rc"): No such file or directory 1104581242 M * we2by I really need a doc on this 1104581244 M * we2by :-( 1104581318 M * _are_ what's in /usr/local/etc/vservers/t/fstab? 1104581342 M * we2by [root@localhost t]# cat /usr/local/etc/vservers/t/fstab 1104581342 M * we2by none /proc proc defaults 0 0 1104581342 M * we2by none /tmp tmpfs size=16m,mode=1777 0 0 1104581342 M * we2by none /dev/pts devpts gid=5,mode=620 0 0 1104581379 M * _are_ ok, still assume your vserver root is buggy, 1104581402 M * _are_ does /usr/local/etc/vservers/t/vdir/etc exist? 1104581420 M * we2by yes, it does 1104581626 M * we2by [root@localhost rc.d]# ls /usr/local/etc/vservers/t/vdir/etc/rc.d 1104581626 M * we2by init.d rc rc0.d rc1.d rc2.d rc3.d rc4.d rc5.d rc6.d rc.local rc.sysinit 1104582122 M * sannes morning :) 1104582426 M * we2by morning sannes 1104582439 M * we2by I need help with making a vserver 1104582449 M * we2by I have my kernel compiled and working 1104584003 J * serving_ ~serving@213.186.171.60 1104584037 Q * serving Read error: No route to host 1104584215 M * _are_ we2by: how you installed the chrooted server? manually? copied from somewhere? or used the vserver tools? 1104584233 M * we2by the chrooted server? 1104584239 M * we2by do u mean the skel? 1104584274 M * _are_ you have only a skeleton? 1104584288 M * we2by yep, I used a script to do it 1104584343 M * _are_ hmm, that might e the reason, I'd say whatever is in there is not enough to run a linux server 1104584361 M * we2by _are_, how should I do it? 1104584364 M * _are_ e.g. /bin/sh might be missing 1104584368 M * we2by can u write a doc how to setup one? 1104584375 M * we2by that would be very nice for newbies 1104584375 M * _are_ what distribution do you use? 1104584380 M * we2by I use fc2 1104584384 M * _are_ hehe, I am a newbie myself 1104584389 M * we2by lol 1104584436 M * _are_ I use debian and instaled my 1st server with vserver-build -m debootstrap 1104584455 M * _are_ i guess vserver-build -m apt-rpm works for fc2 1104584455 M * we2by kernel version? 1104584479 M * we2by vserver-build don have this one 1104584531 M * _are_ it is in /usr/lib/util-vserver/vserver-build here 1104584532 M * we2by ok, so first u do a kernel recompile with vserver support 1104584540 M * _are_ yes 1104584546 M * we2by then? 1104584563 M * _are_ then i built the tols and instaled them 1104584572 M * _are_ and then i just used this command and set it up 1104584597 M * we2by and it worked ok? 1104584603 M * _are_ my problems started later with more network cards, mount --bind and so on 1104584605 M * _are_ yes 1104584617 M * we2by debian version 1104584620 M * we2by kernel version 1104584626 M * we2by patch version 1104584627 M * we2by please 1104584671 M * _are_ won't help much, as I run on dual opteron and therefore use an inofficial debian version 'debian-amd64' (sarge/sid) 1104584673 M * we2by and the utilities version u used 1104584680 M * we2by :-( 1104584693 M * _are_ Linux master1a 2.6.10-vs1.9.3.14 #1 SMP Mon Dec 27 16:20:13 CET 2004 x86_64 GNU/Linux 1104584709 M * we2by I have the same kernel version 1104584711 M * we2by same patch 1104584718 M * _are_ util-vserver-0.30.196 1104584736 M * we2by I got that also 1104584891 M * we2by then what did u do to make a vserver? 1104585085 M * _are_ vserver-build -m debootstrap -n base32 --context 111 --hostname base32 --interface 10.1.10.11 -- -d sarge --arch i386 --mirror http://web/mirror/debian/ 1104585472 M * we2by yea, I reading this http://linux-vserver.org/DebianVserver 1104585479 M * we2by the vserver documentation is very poor 1104585481 M * we2by :-( 1104585490 M * _are_ well, especially on the new tools :-) 1104585510 M * _are_ feel free to write down everything you find out, this is why the wiki is there. 1104586245 Q * we2by Ping timeout: 480 seconds 1104587783 Q * sannes Read error: Connection reset by peer 1104588472 J * we2by ~Jinxi@145.116.4.79 1104588509 M * we2by _are_, u still there? 1104588528 M * _are_ we2by: yes 1104588538 M * we2by did u build the utilities from source? 1104588544 M * we2by are install it from deb packages? 1104588549 M * we2by or* 1104588922 M * _are_ source 1104588940 M * _are_ the deb packages that have been avaliable 2 weeks ago had been old style tools 1104589174 M * we2by I don care if it? old 1104589174 M * we2by :\ 1104589186 M * we2by _are_, I will do what u did there 1104589198 M * we2by sicnce debian use kernel 2.4 , it would be much better 1104589208 M * we2by the 2.6 is not stable version 1104589480 J * are|lunch ~are@dsl-084-056-154-109.arcor-ip.net 1104589543 M * are|lunch hmpf, some random-hour disconnect (not the usual 24 at least, something loner 1104589573 Q * _are_ Ping timeout: 480 seconds 1104589584 N * are|lunch _are_ 1104589620 M * _are_ we2by: 15:15 <_are_> source 1104589620 M * _are_ 15:15 <_are_> the deb packages that have been avaliable 2 weeks ago had been old style tools 1104590998 M * _are_ is there any documentation about unifying servers with the new util-vserver? 1104592024 M * we2by _are_, after installing the kernel and the utilities, what should I do? 1104592064 M * _are_ do the equivalent for your distribution for: vserver-build -m debootstrap -n base32 --context 111 --hostname base32 --interface 10.1.10.11 -- -d sarge --arch i386 --mirror http://web/mirror/debian/ 1104592076 Q * v00dY Remote host closed the connection 1104592136 J * sannes ~ace@home.skarby.no 1104592180 M * we2by it? my first time installing and using debian 1104592185 M * we2by hope it? easy 1104592496 M * _are_ vserver-uild is part of util-vserver and seems you could run it via vserver ... build, too, it is in util-vserver-0.30.196/scripts/vserver-build in the source or here, installed in /usr/lib/util-vserver/vserver-build 1104593035 Q * t____ Ping timeout: 480 seconds 1104593059 J * t____ ~tnichols@CPE-139-168-210-192.sa.bigpond.net.au 1104593060 M * sannes hm, hah! got a freez without preempt now.. great! :> plain 2.6.10 with vs .. but it "ran" stable for a lot of hours .. almost fooled me.. 1104593095 M * _are_ mine is up for 4 days now and users on it, too 1104593118 M * _are_ but i turned off everything that has been marked as experimental 1104593119 M * sannes lucky you :) 1104594142 M * sannes did the same thing, nothing experimental in the kernel.. 1104594176 M * _are_ i have an smp kernel 1104594230 M * sannes I had problems on both smp kernels and single cpu kernels.. 1104594242 M * sannes what filesystem are you using? 1104594246 M * sannes or filesystems.. 1104594340 M * _are_ started with reiserfs, the vservers run there 1104594350 M * _are_ some new filesystems have ext3 1104594377 M * _are_ i have opterons here, that means I try and run 64-bit linux and one Idea for the instability was reiserfs 64-bit cleanness 1104594396 M * _are_ so i started and migrate, but the box is stable now, it seems 1104594402 M * _are_ so no further migration 1104594511 Q * Guest2 Quit: leaving 1104594958 M * sannes ah 1104595010 M * sannes well, I'm running on x86 so.. what can I say .. maybe it is architecture dependent the bug I'm experiencing.. 1104595109 M * _are_ x86 most use, including bertl, so I'd assume it to be the most stable. 1104595181 M * sannes so would I, doesn't mean it is true 1104595219 M * sannes because what I am experiencing is real, and two seperat computers do completly freeze.. 1104595243 M * _are_ hmm, what hardwared o you use? 1104595264 M * _are_ I had bad experiences with linux and some aic79xx scsi adaptor in 2.4 kernels 1104595652 M * sannes ah, well, no troubles with either of the computers before.. one is a laptop Pentium 4 M (centrino?) and the other is a Pentium 4 Xeon .. 1104595911 M * Doener evening! 1104597640 M * sannes :) 1104599454 M * sannes heh.. a cute kernel panic.. 1104601904 Q * TheSeer Remote host closed the connection 1104602101 J * TheSeer ~theseer@border.office.salesemotion.net 1104602841 N * Bertl_zZ Bertl 1104602849 M * Bertl morning folks! and a happy new year! 1104604092 M * Bertl sannes: how is the vroot device? 1104604381 J * DuckKing ~Duck@dyn-83-157-130-113.ppp.tiscali.fr 1104604394 M * Bertl welcome DuckKing! 1104604775 Q * serving_ Read error: Connection reset by peer 1104604815 Q * DuckMaster Ping timeout: 480 seconds 1104606560 Q * we2by Ping timeout: 480 seconds 1104606581 J * we2by ~Jinxi@dc5146d009.adsl.wanadoo.nl 1104606978 M * we2by after ptaching the 2.4.x kernel and I don see vserver when doing make menuconfig, is this ok? 1104606982 M * we2by or i did it wrong? 1104607006 M * Bertl hey we2by! what kernel and what patch? 1104607024 M * we2by 2.4.28 and this patch http://www.13thfloor.at/vserver/s_release/v1.29/ 1104607034 M * we2by http://www.13thfloor.at/vserver/s_release/v1.29/patch-2.4.28-vs1.29.diff.gz 1104607068 M * Bertl that's fine, the only config option is the vroot here 1104607368 M * we2by berni, after booting up the kernel, how do I know my kernel is running with vserver support? 1104607512 M * Bertl I'm not berni, but I'll answer anyways: just run the test script (http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh) 1104607770 M * we2by I got my kernel 1104607775 M * we2by so I need the utilities now 1104607813 M * we2by http://www.13thfloor.at/vserver/s_release/v1.29/util-vserver-0.30.tar.bz2 this one would work with 2.4.28 ? 1104608139 M * we2by utilities installed 1104608144 M * we2by what's next? 1104608150 M * we2by _are_, u still there? 1104608177 M * we2by where can I get vserver-build> 1104608178 M * we2by ? 1104608218 M * Bertl vserver-build is part of the alpha util-vserver ... 1104608244 M * we2by I ahve the 0.3 version. so no vserver-build for me 1104608253 M * we2by berni, what do I do now? 1104608257 M * Bertl so if you want that functionality, you have to install util-server-0.30.196 (or later) 1104608259 M * we2by I mean I want to make vserver 1104608662 M * we2by berni, I don know how to setup a vserver 1104608676 M * we2by I just got my kernel compiled and running and have the utilities installed 1104608682 M * we2by Bertl, 1104608690 M * Bertl yes? 1104608732 M * we2by read that ^ 1104608756 M * Bertl well, you have different options ... you can get one of the prepared images 1104608768 M * we2by yea, that? the easiest way to go 1104608798 M * Bertl or you can copy an existing server to a directory 1104608830 M * we2by Bertl, which one is the best according to you? 1104608867 M * Bertl I would install the alpha util-vserver and do something like 'vserver build -m ...' 1104608903 M * Bertl but there is also a build tool in the 0.30 package .. sec 1104608935 M * Bertl yep, it's called newvserver 1104608982 M * we2by I don have that 1104608986 M * Bertl (it's an interactive tool, which work from/with linuxconfig) 1104609019 M * we2by so I need linuxconfig? 1104609033 M * Bertl to use that tool, I guess yes ... 1104609071 M * Bertl # rpm -ql -p /usr/src/RPM/RPMS/i586/util-vserver-0.30-1mdk.i586.rpm | grep newvserver 1104609074 M * we2by now 1104609074 M * Bertl /usr/sbin/newvserver 1104609077 M * Bertl /usr/share/man/man8/newvserver.8.bz2 1104609092 M * we2by what version? 1104609138 M * Bertl I don't think that it is very linuxconfig vsersion specific ... 1104609158 M * we2by I can install the alpha version 1104609172 M * we2by the 0.3 verion is installed under /usr/local anyway 1104609177 M * Bertl of linuxconfig or util-vserver? 1104609273 M * we2by http://www.lycos-vds.com/dists/ 1104609280 M * we2by Bertl, why are those images so small? 1104609293 M * we2by isn a image of a distro be over a few 100mbs? 1104609344 M * Bertl the images a (almost) minimal .. so they don't contain various stuff you would need/find on a typical isntallation 1104609358 M * Bertl and they are compressed ... 1104609373 M * we2by Bertl, the aplpha version is for vserver 1.9 1104609377 M * we2by this is kernel 2.4 1104609389 M * we2by and vserver 1.29 1104609393 M * Bertl alpha util-vserver works for both, 2.4 and 2.6 1104609445 M * we2by Bertl, I am lost now. k. I get the iamge 1104609455 M * we2by I downloaded the debian image 1104609461 M * we2by so, what;s next? 1104609513 M * Bertl unpack it somewhere (e.g. /vservers/xxx) , create a minimal config for that vserver, and start it 1104609582 M * we2by ok, I need a howto on creating the config? 1104609591 M * we2by Bertl, any link? 1104609689 M * Bertl something like this in /etc/vservers/xxx.conf 1104609692 M * Bertl ONBOOT=yes 1104609692 M * Bertl ULIMIT="-HS -c 0 -n 1024 -u 500" 1104609692 M * Bertl S_CONTEXT=100 1104610002 M * we2by Bertl, is that enough to start a vserver? 1104610010 M * Bertl yep 1104610014 M * we2by I have had problems with proc yesterday 1104610028 M * we2by but it was kernel 2.6.10 1104610033 M * Bertl 2.4 kernel has proc security turned off, so no issues there 1104610112 M * Bertl and for 2.6 the vprocunhide script takes care of that 1104610126 M * we2by yea, I hide it 1104610137 M * we2by but got a second error on /etc/rc.d/rc 1104610145 M * we2by hope this one works 1104610819 M * we2by Bertl, how do my kernel know I put vserver server1 in /vserver/server1 ? 1104610853 M * Bertl you should put it in /vservers/server1 then make a config in /etc/vservers/server1.conf 1104610863 M * Bertl the if you do vserver server1 start 1104610872 M * we2by debian:/vservers/server1# vserver server1 start 1104610872 M * we2by No configuration for this vserver: /etc/vservers/server1.conf 1104610877 M * Bertl it will check the config and start the according vserver 1104610880 M * sannes Bertl :) 1104610896 M * sannes Bertl : get operation not permitted trying to activate quota.. 1104610898 M * we2by how do I tell vserver my configs are in /usr/local and not in /etc? 1104610916 M * Bertl at compile time (with configure) 1104610991 M * we2by ok, how do I know it? started? 1104610992 M * we2by :\ 1104611020 M * Bertl vserver-stat 1104611043 M * we2by nice 1104611046 M * we2by it? started 1104611053 M * we2by now I have to config the network 1104611080 M * Bertl add something like: 1104611095 M * Bertl IPROOT="eth0:192.168.0.1" 1104611106 M * Bertl to the config, after you stopped the vserver 1104611126 M * we2by nice 1104611143 M * we2by when I have 2 or more vservers, and each one has its own ip 1104611165 M * we2by would vserver auto configure my network card to have multiple ip?? 1104611195 M * Bertl with the config I showed, it will create an alias 1104611219 M * we2by awsome 1104611222 M * we2by yea, this is so cool 1104611227 M * we2by thaks alot Bertl 1104611249 M * Bertl ur welcome! 1104611321 M * we2by Bertl, does the fc2 image work on a debian host too? 1104611704 M * sannes Bertl : do i need some capability to do the mount stuff? 1104611719 M * sannes Bertl : ugh, not mount stuff, quotaon .. 1104611737 J * serving ~serving@213.186.171.95 1104611744 M * we2by umm I don know the password 1104611757 M * we2by the root password 1104611788 M * Bertl well, you can 'edit' it on the host, right? 1104611824 M * we2by it is etc/shadow right? 1104611852 M * Bertl sannes: hmm, no should work, but maybe 2.6 has stricter security ... I can check if you get permission issues ... 1104612211 M * we2by Bertl, how do I enter the vserver? 1104612233 M * Doener we2by: just chroot into the right directory and use passwd to change the password 1104612245 M * we2by I know, I just changed the pass 1104612247 M * Bertl either via ssh, or with 'vserver enter' 1104612258 M * Doener ok ;) 1104612300 M * we2by I can ssh into it 1104612303 M * we2by can;t 1104612363 M * Doener you have to configure the ssh daemon on the host, so that it only listens on a limited set of ip addresses 1104612377 M * we2by I did that 1104612385 M * we2by I config it to bind to 10.0.0.25 1104612394 M * we2by and the vserver is on 10.0.0.26 1104612416 M * Doener when starting the vserver, did you get any failure messages? 1104612443 M * we2by Starting MTA: cat: /etc/mailname: No such file or directory 1104612443 M * we2by exim4. 1104612445 M * we2by only that 1104612445 M * Bertl happy new year Doener! 1104612475 M * Doener Bertl: same to you, let's make this the year of Linux-VServer :-) 1104612524 M * we2by debian:/# ping google.com 1104612524 M * we2by ping: icmp open socket: Operation not permitted 1104612530 M * we2by within the vserver 1104612558 M * Bertl that's fine .. you are not supposed to 'ping' from inside (for security reasons) 1104612564 M * Doener we2by: that's expected, you need CAP_NET_RAW to use ping, but that also allows sniffing network traffic 1104612574 M * we2by mh, yea. 1104612588 M * we2by just put that in the config file. right? 1104612666 M * Doener if you absolutely need 'ping', yes. but you normally don't really need it, do you? 1104612673 M * Bertl Doener: 2005, the year of the Linux-VServer ... I like it ;) 1104612679 M * we2by Doener, nope 1104612721 M * Doener ok :) did you get any messages about ssh on vserver start? 1104612841 M * we2by wait, I need to install a few commands 1104612866 M * we2by same error 1104612947 M * we2by Doener, nope 1104612961 M * Doener maybe it's just not installed then... 1104612995 M * we2by there is no host key 1104613001 M * we2by how do generate those keys 1104613018 M * Bertl ssh-keygen 1104613078 M * Doener Bertl: what's the reason for having xid in the task_struct in addition to vx_info? 1104613176 M * Bertl 90% of the checks are xid based, no need to dereference vx_info 1104613197 M * Bertl (avoids cache flushes, kernel panics ...) 1104613325 M * Doener thought so, just wanted a confirmation ;) 1104613463 M * Bertl in theory vx_info would be enough, tests showed, that it isn't a good idea ... 1104613519 M * we2by what is the permission for these keys? 1104613545 M * Doener 0400 i'd say... 1104613821 M * we2by it? working 1104613823 M * we2by cool 1104613837 M * Bertl fascinating stuff, isn't it? 1104613857 M * we2by yea 1104613879 M * we2by the greatest thing is that it does not eat up all my cpu 1104613902 M * Bertl yes, the overhead is minimal (below 2% last time we checked) 1104614050 M * we2by I added CAP_NET_RAW 1104614055 M * we2by but ping still does not work 1104614066 M * Doener did you restart the vserver? 1104614071 M * we2by yep 1104614084 M * Doener how does your line containing CAP_NET_RAW look like? 1104614115 M * we2by just that 1104614128 M * we2by do I need something else 1104614143 M * we2by debian:~# cat /etc/vservers/server1.conf 1104614143 M * we2by ONBOOT=yes 1104614143 M * we2by ULIMIT="-HS -c 0 -n 1024 -u 500" 1104614143 M * we2by S_CONTEXT=100 1104614143 M * we2by IPROOT="eth0:10.0.0.26" 1104614143 M * we2by CAP_NET_RAW 1104614151 M * Doener should be: S_CAPS="CAP_NET_RAW" 1104614180 M * we2by is there a doc I can learn more about this config 1104614181 M * we2by ? 1104614275 M * Bertl Doener: as the rcu oops is still not resolved, I reactivated the history stuff (see source for details ;) and here is the first trace: http://vserver.13thfloor.at/Experimental/OOPS/2.6.10-vs1.9.3.14.6.log 1104614292 M * Doener we2by: there's an example in the vserver script itself IIRC 1104614306 M * Bertl I'm off for some cooking now ... back later ... 1104614310 N * Bertl Bertl_oO 1104616305 M * Doener Bertl_oO: i get rejects/problems with the .14.x with starting with .14.3->.14.4 1104618788 Q * we2by Quit: Ik ga weg 1104618794 J * we2by ~we2by@dc5146d009.adsl.wanadoo.nl 1104623912 J * yarihm ~yarihm@217-162-204-130.dclient.hispeed.ch 1104623916 M * yarihm hi everyone 1104623926 M * Doener hi yarihm 1104623998 M * yarihm i have a often asked question i guess, thus i don't want to ask without asking for a FAQ regarding 2.6.10 (handling a not propperly applying patch and searching for a solution) ... any hints? :)