1107907497 Q * comdata Remote host closed the connection 1107911643 Q * Hollow Remote host closed the connection 1107924416 J * nox- ~nox@c135038.adsl.hansenet.de 1107924455 Q * nox Read error: Connection reset by peer 1107924476 N * nox- nox 1107925049 Q * monrad Quit: Leaving 1107927551 J * monrad ~monrad@213083190130.sonofon.dk 1107934417 Q * SiD3WiNDR Ping timeout: 480 seconds 1107934700 J * SiD3WiNDR luser@bastard-operator.from-hell.be 1107937533 M * halorgium ping..... 1107937587 M * mugwump ping 1107937600 M * mugwump er, I mean pong 1107937888 M * halorgium :) 1107937915 M * halorgium pondering a way to put a /sbin/agetty into ttyX ... 1107937952 M * halorgium i tried like /usr/sbin/vserver $VSERVER suexec /sbin/agetty ... ... 1107937959 M * halorgium didn't like that :( 1107938039 M * mugwump you want a getty in a vserver to gett a real tty from the console? 1107938054 M * mugwump did you make sure that /dev/ttyX was in the vserver's /dev ? 1107938230 M * halorgium yip 1107938240 M * halorgium um ... didn't do the second one though 1107938242 M * halorgium *tries* 1107938284 J * prae ~prae@ezoffice.mandrakesoft.com 1107938328 M * halorgium hrm .... /dev/tty6 exists ... i suppose that is to be expected :) 1107938559 M * mugwump so /vservers/xxx/dev/tty6 is there, and you're starting the getty with the above command 1107938582 M * mugwump does it fail with a message? 1107938904 M * halorgium /sbin/init q doesn't actually attempt to reload the /etc/inittab :( 1107938951 M * mugwump normally, the process visible as `init' inside a vserver is actually a dummy process 1107938976 M * mugwump it is possible to set up a real init to run, you need to set a flag on the vserver configuration 1107938982 M * mugwump called "fakeinit" or something iirc 1107939136 M * halorgium hrm ... i might have a look into that tomorrow 1107939146 A * halorgium is just setting up rt3 :) 1107939189 M * mugwump rt3++ 1107939211 M * mugwump I've found it works best in FastCGI mode (search for FastCGI on its wiki) 1107939874 M * halorgium mugwump: speaking on rt3 now ... would you suggest a seperate `queue' for $CLIENT_EMAIL and $CLIENT_WEB etc? 1107939910 M * mugwump not sure what that question means tbh, are those SiteConfig.pm options? 1107939958 A * mugwump blushes and realises they aren't 1107939974 M * halorgium nah ... arbitary vars :) 1107939996 M * mugwump It should be possible to use a single queue for both, so long as the ACLs are correctly configured 1107940002 M * halorgium just pondering whether to have a queue for a whole client ... or have multiple queues for each clients ... 1107940011 M * halorgium it is more a logistics thing ... 1107940035 M * halorgium some people won't be interested in website issues ... or email issues 1107940064 M * mugwump yeah. you definitely need to group them up by mood of the people looking at them :) 1107940083 M * halorgium mmm ... just thought i'd ask ;) 1107940089 M * mugwump (required mood to serve these tickets well) 1107940097 M * halorgium you might have said ... noooooooooo, don't do that! 1107940106 M * halorgium lol ... indeed 1107940132 M * mugwump it's really easy to join queues together later 1107940145 M * mugwump and also to move all tickets that match a search function into another queue 1107941351 J * rs rs@ice.aspic.com 1107942660 M * rs hi 1107943980 M * halorgium 'lo 1107944004 N * Bertl_zZ Bertl 1107944008 M * Bertl morning folks! 1107944029 M * halorgium lol ... tis 23:14 here :) 1107944065 M * Bertl halorgium: well, that's 23:14 in the morning, right? ;) 1107944188 M * mugwump almost morning here 1107944204 M * mugwump well, if you consider a.m. to mean morning ;) 1107944274 M * halorgium mugwump: tis true :) 1107944322 M * mugwump hey you're in my time zone halorgium 1107944445 M * mugwump do you know broquaint, halorgium ? 1107944505 M * halorgium mugwump: #nzbt on undernet 1107944522 M * halorgium um ... no 1107946726 M * SiD3WiNDR odd newzealanders, 12 hours behind :p 1107947123 M * Bertl rs: any test status/plans/etc? 1107947144 M * Bertl (just curious) 1107947393 M * rs Actually I got few more things to do :/ 1107947412 M * rs I should be ready for tests soon (c) 1107947452 M * Bertl heh, no problem ... 1107948683 M * Bertl okay, back later ... 1107948691 N * Bertl Bertl_oO 1107950809 N * Bertl_oO Bertl 1107950825 M * Bertl back now ... ;) 1107955723 J * are|lunch ~are@82.139.196.122 1107955739 M * Bertl welcome are|lunch! ;) 1107956281 N * BobR_oO BobR 1107956295 M * are|lunch if I gave it: definitly 1107956308 M * are|lunch umpf, should learn to use my keyboard 1107956313 N * are|lunch _are_ 1107956322 M * _are_ renaming was what I meant to do. 1107956323 M * _are_ Hi 1107957154 J * mhepp ~mhepp@r72s22p13.home.nbox.cz 1107957807 M * Bertl welcome mhepp! 1107957818 M * Bertl back a little later ... 1107957824 N * Bertl Bertl_oO 1107959142 Q * Loki|muh Ping timeout: 480 seconds 1107959430 J * Loki|muh loki@213.133.125.66 1107960593 N * BobR BobR_oO 1107960649 J * sod ~sod@adisamopensystems.iasi.rdsnet.ro 1107960653 M * sod helo 1107960699 M * sod I used to have a working vserver setup; a few minutes ago the server was rebooted and the vservers won't start 1107960718 M * sod I keep getting the permission denied whne mounting /proc 1107960720 M * sod in vservers 1107960728 M * sod a ran the vprocunhide script 1107960856 Q * ndim Ping timeout: 480 seconds 1107961226 J * ndim U2FsdGVkX1@helena.bawue.de 1107961691 M * _are_ sod: no mounting inside vservers, you have to mount it outside 1107961767 M * sod proc on /proc type proc (rw) 1107961772 M * sod I have this in master 1107961788 M * sod when I do a vserver start 1107961799 M * sod I get the error that /proc is not mounted 1107961812 M * _are_ yes, that is the /proc inside the vserver 1107961827 M * _are_ do you have old (filebased) or new (directorybased) configuration? 1107961827 M * sod yeap 1107961832 M * sod old 1107961835 M * sod but it worked 1107961852 N * Bertl_oO Bertl 1107961859 M * sod this is weird 1107961861 M * _are_ hmm, ok, I have basically no knowledge about the old configuration, I only ever used the new one 1107961884 M * Bertl sod: proc security! 1107961885 M * _are_ however, in new configuration you have an 'fstab' file for the vserver and the startup script mounts the contants inside the vserver on startup 1107961919 M * sod Bertl: yes, it's obvoius 1107961931 M * sod but I've ran the vprocunhide script 1107961944 M * sod and, I repeat, this setup used to work 1107961948 M * Bertl you are on 2.6 kernel, right? 1107961950 M * sod yeap 1107961968 M * Bertl okay, you did run the vprocunhide on the master right after reboot, right? 1107961978 M * sod yes, right after 1107961988 M * sod and several times siche then 1107961995 M * sod s/siche/since 1107961996 M * Bertl okay, when you do 'chcontext --ctx 1 top' 1107962002 M * Bertl does that work? 1107962049 M * sod nope 1107962073 M * sod it exists right after 1107962073 M * Bertl what tool/kernel version do you use? 1107962171 M * sod patch-2.6.9-vs1.9.3.diff.bz2 util-vserver-0.30.196 1107962185 M * Bertl okay, let's give this a try: 1107962188 M * Bertl http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh 1107962199 M * Bertl run it on the host, and let me know what it says ... 1107962233 M * sod backup:/tmp# sh testme.sh 1107962234 M * sod Linux-VServer Test [V0.09] (C) 2003-2005 H.Poetzl 1107962234 M * sod chcontext is working. 1107962234 M * sod chbind is working. 1107962234 M * sod Linux 2.6.9-vs1.9.3 i686/0.30/0.30 [J] 1107962234 M * sod --- 1107962236 M * sod [001]# succeeded. 1107962238 M * sod [011]# succeeded. 1107962240 M * sod [031]# succeeded. 1107962242 M * sod [101]# succeeded. 1107962244 M * sod [102]# succeeded. 1107962246 M * sod [201]# succeeded. 1107962248 M * sod [202]# succeeded. 1107962266 M * Bertl so, to me it looks like you mixed tool versions 1107962278 M * Bertl the testme.sh reports the stable utils (0.30) 1107962291 M * Bertl while you are using the alpha utils (0.30.196) 1107962343 M * sod ok, what next.. 1107962353 M * Bertl (see chcontext --version for that) 1107962362 M * sod I remeber get very weird errors when I tried to use the alpha version 1107962369 M * Bertl you should try to deinstall the stable tools 1107962400 M * Bertl and after that reinstall the alpha-tools ... 1107962424 M * Bertl I'm pretty sure vprocunhide and friends will start working once the tools are properly installed 1107962502 M * sod ok, let's try 1107963086 M * sod same shit :( 1107963101 M * Bertl what distro? 1107963106 J * hansi33 ~hansi33@193.80.53.173 1107963115 M * Bertl welcome hansi33! 1107963146 M * Bertl sod: and check what chcontext --version reports ... 1107963156 M * hansi33 hello Bertl 1107963168 M * sod backup:~# chcontext --version 1107963168 M * sod chcontext 0.30.196 -- allocates/enters a security context 1107963168 M * sod This program is part of util-vserver 0.30.196 1107963168 M * sod Copyright (C) 2004 Enrico Scholz 1107963168 M * sod This program is free software; you may redistribute it under the terms of 1107963168 M * sod the GNU General Public License. This program has absolutely no warranty. 1107963191 M * Bertl well, that looks good ... 1107963202 M * Bertl now let's redo the testme.sh 1107963214 M * Bertl (just the first three lines are of interest to me) 1107963233 M * sod chcontext is working. 1107963233 M * sod chbind is working. 1107963233 M * sod Linux 2.6.9-vs1.9.3 i686/0.30.196/0.30.196 [Ea] 1107963240 M * Bertl looks much better ... 1107963248 M * Bertl now let's use the vprocunhide 1107963254 M * sod already did 1107963260 M * Bertl and try again with the chcontext --ctx 1 top 1107963260 M * sod still does not work 1107963263 M * sod ok 1107963429 M * Bertl does this work for you now? 1107963541 M * sod nope, sorry 1107963555 M * sod backup:/usr/local/lib/util-vserver# ./vprocunhide 1107963555 M * sod ./vprocunhide: line 26: : No such file or directory 1107963557 M * Bertl okay, let's try: setattr -R --~hide /proc 1107963561 M * sod this is fucked up 1107963568 M * sod this one used to work 1107963573 M * Bertl yeah, well, you f* it up ... ;) 1107963581 M * sod yeap, prolly :) 1107963584 M * Bertl setattr -R --~hide /proc 1107963594 M * Bertl this will disable the proc security for now ... 1107963708 M * sod ok 1107964063 M * sod nope, it does not work 1107964065 M * sod wtf 1107964140 M * Bertl pardon? 1107964155 M * Bertl what does not work? 1107964168 M * sod backup:/usr/local/lib/util-vserver# vserver backup01 enter 1107964168 M * sod WARNING: can not find configuration, assuming legacy method 1107964168 M * sod ipv4root is now 69.93.182.139 1107964168 M * sod chcontext: vc_new_s_context(): Operation not permitted 1107964181 M * sod but chcontext --ctx 1 top works 1107964197 M * Bertl probably that is because you are using dynamic contexts 1107964214 M * Bertl (which are depreciated for some time now, just debian still uses them by default) 1107964241 M * Bertl you should use a line like this: S_CONTEXT=100 in your config 1107964337 M * sod same stuff 1107964383 M * Bertl you have to restart that vserver first 1107964399 M * Bertl (it doesn't work _after_ you started the vserver) 1107965073 Q * tchan Quit: leaving 1107965128 J * tchan ~tchan@c-24-13-81-164.client.comcast.net 1107965218 M * sod ok, it's like this 1107965227 Q * mhepp Quit: mhepp caught signal: Autobus error 1107965230 M * sod and that's how I got it working the first time 1107965241 M * sod I install the alpha tree for the utils 1107965250 M * sod I run the vprocunhide 1107965262 M * sod and the I have to use the stable tree 1107965272 M * sod becuase alpha doesn't work 1107965364 M * Bertl okay, you still didn't answer my question regarding your distro ... 1107965809 M * sod oh, sorry, it's a debian sarge 1107965819 M * Bertl thought so ... 1107965826 M * sod I was busy getting everything up again 1107965837 M * Doener sod: which kernel version? 1107965852 M * Bertl there are supposed-to-be-working debian apckages floating around .. 1107965863 M * sod 2.6.9-vs1.9.3 1107965865 M * Bertl (for both, the kernel and the alpha tools) 1107965866 J * marmotte ~marmotte@abo-80-50-68.mts.modulonet.fr 1107965870 M * Bertl welcome marmotte! 1107965894 M * Doener sod: that one contains a bug that breaks 'vserver xxx enter' for legacy configs 1107965912 M * Doener Bertl: it's the CAP_CONTEXT check bug, if you remember that one... 1107965945 M * Bertl yes, of course, but that should not apply to static contexts and new tools, right? 1107965978 M * Doener it applies to new tools + legacy config, static/dynamic doesn't matter 1107966006 M * Bertl hmm ... 1107966017 M * sod ok, what can I do? 1107966021 M * Bertl sod: did you compile the kernel yourself? 1107966029 M * Doener the tools call sys_vserver twice, and the alpha tools, in contrast to the stable tools, check if the second call suceeds, and it does not, since the context misses CAP_CONTEXT 1107966037 M * sod Bertl: yes 1107966052 M * Bertl okay, then please try to upgrade to 1.9.4-rc5 (or rc4 at least) 1107966064 M * Bertl http://vserver.13thfloor.at/Experimental/RC-1.9.4/ 1107966081 M * Doener so stable tools work (probably only with static context), and alpha tools work with new config style 1107966094 M * marmotte Bertl: hello ! 1107966132 M * marmotte i have an other problem with virtual server on kernel 2.6.10 1107966150 M * sod Bertl: ok 1107966152 M * sod will do 1107966154 M * marmotte i have this message each time i start a vserver 1107966159 M * sod I have to schedule a downtime 1107966171 M * sod this already took me one hour to solve 1107966176 M * Bertl sod: you can also get newer tools, but they should work (btw, stable tools should work too) 1107966214 M * marmotte Error: /proc must be mounted 1107966221 M * marmotte To mount /proc at boot you need an /etc/fstab line like: 1107966223 M * Bertl proc security *sigh* 1107966228 M * sod :) 1107966244 M * marmotte but the vserver starts 1107966245 M * Bertl marmotte: debian? 1107966247 M * sod maybe you should set a topic regarding the proc issue :) 1107966250 M * marmotte but i can't stop it 1107966256 M * marmotte Bertl: yes Debian Sid 1107966279 M * Bertl http://linux-vserver.org/Proc-Security 1107966285 M * sod ok, let's figure out a way to get debian and vserver working 1107966286 M * aba marmotte: debian sid doesn't have the newest tools. See the bug reports. 1107966304 M * sod I'll try the new kernel patch 1107966316 M * marmotte aba: and this is for this reason ? 1107966329 M * Bertl sod, marmotte: there are at least three different aspects 1107966333 M * aba marmotte: that they were not uploaded. 1107966342 A * sod taking notes 1107966349 M * Bertl - stable vs devel (don't mix if not necessary) 1107966365 A * marmotte listening 1107966374 M * Bertl - always make sure to get recent/latest tools 1107966392 M * Bertl - avoid the 'typical' debian packages like hell 1107966400 M * sod ok 1107966405 M * Bertl (the last one is currently being addressed) 1107966411 M * marmotte Bertl: like hell ? woaw !! 1107966430 M * Bertl i.e. some debian folks are trying to get recent tools/kernels into debian-whatever ... 1107966437 M * sod 1222 49153 UNKNOWN ? Ss 0:00 /usr/sbin/cron 1107966442 M * sod from vps 1107966447 M * sod why UNKNOWN 1107966450 M * Bertl ah, and I almost forgot ... 1107966474 M * marmotte So i have to take utils from source, compile them, and i have greater chance it will work? nothing to do with /proc ? 1107966476 M * Bertl do not use the debian vserver config, it's broken in so many regards 1107966500 M * Bertl sod: is there sensitive information in your .conf ? 1107966505 M * marmotte Bertl: should i change my distrib ? ;-) 1107966521 M * marmotte Bertl: no, i can give you my conf 1107966528 M * Bertl okay, paste it here ... 1107966557 M * marmotte # cat /etc/vservers/web.conf 1107966559 M * marmotte S_HOSTNAME="web" 1107966563 M * marmotte IPROOT="eth1.1:10.0.0.1" 1107966573 M * marmotte S_NICE="" 1107966579 M * marmotte S_FLAGS="lock nproc" 1107966584 M * marmotte ULIMIT="-H -n 1024" 1107966588 M * marmotte S_CAPS="CAP_NET_RAW" 1107966592 M * marmotte S_DOMAINNAME="" 1107966597 M * marmotte (EOF) 1107966600 M * Bertl okay, almost a typical debian config 1107966609 M * Bertl you got rid of the IPROOTDEV= already 1107966624 M * Bertl after a cleanup, it would look like this: 1107966626 M * marmotte yes, it's in comment 1107966635 M * Bertl S_FLAGS="nproc" 1107966641 M * Bertl ULIMIT="-HS -n 1024" 1107966646 M * Bertl S_CAPS="" 1107966651 M * Bertl S_CONTEXT=1001 1107966664 M * Bertl (not listed entries are unchanged) 1107966683 M * marmotte ok, i do the changes 1107966685 M * Bertl lock - doesn't make sense ... 1107966697 M * Bertl -H -> -HS save you from a lot of issues 1107966718 M * Bertl CAP_NET_RAW - not required, just makes the vserver insecure 1107966741 M * Bertl S_CONTEXT= - static contexts are preferred, dynamic ones deprecated 1107966756 M * marmotte stil the /proc error 1107966775 M * Bertl yes, of course ... 1107966786 M * sod Bertl: so, we have to use different S_CONTEXT for each vserver 1107966788 M * sod right? 1107966800 M * Bertl marmotte: that is unrelated, you have to configure the proc security on your host 1107966804 M * Bertl sod: yes, correct 1107966805 M * sod like 1001, 1002, 1003, 1004, etc 1107966807 M * sod ok 1107966816 M * Bertl range is between 2 and 49151 1107966826 M * sod got it 1107966831 M * marmotte it has started 1107966853 M * Bertl marmotte: which tools do you use? (version) 1107966872 M * marmotte Bertl: all my vserver debian-configured have context number > 49152 1107966875 M * sod Bertl: what about IPROOTDEV= 1107966882 M * marmotte Bertl: Debian tool 1107966883 M * sod why is it bad? 1107966902 M * Bertl the IPROOTDEV="eth0" for example 1107966909 M * marmotte Bertl: i am going to download the correct one 1107966915 M * Bertl will add jsut this prefix to every address you specify 1107966922 M * sod ok 1107966935 M * sod why is that bad? 1107966936 M * Bertl you can do the same with eth0: 1107966941 M * sod a, ok 1107966956 M * Bertl but, if you want to do (without the eth0) no way, if IPROOTDEV= set 1107967073 M * marmotte on http://linux-vserver.org/Linux-VServer , there is Debian specific tools. should i download them ? 1107967091 M * Bertl they should be the newer ones, I guess ... 1107967105 M * Bertl check version and date ... 1107967122 M * marmotte oops, it is vserver system image, mea culpa 1107967328 A * marmotte thinks that the website is not clear 1107967359 M * Bertl please go ahead and make it clear (after checking what clear is, with some folks ehre on the channel ;) 1107967396 M * marmotte Bertl: ilet me finished my studies, and i will do that 1107967430 M * marmotte let me finish my studies, and i will do that (sorry for my english today) 1107967625 M * marmotte i have found ! http://www.13thfloor.at/vserver/d_rel26/v1.9.3/ 1107967647 M * Bertl yeah? 1107967649 M * sod I think the UNKNOWN stuff is vps are leftovers from my previous attempts to start the whole thing 1107967649 M * marmotte should i download the dev tools ou the stable ones ? 1107967673 M * Bertl depends on what you want to run?! 1107967689 M * marmotte patch for kernel 2.6.10 1107967690 M * Bertl what is the reson for using a 2.6 kernel? 1107967704 M * Bertl (just curious) 1107967733 M * marmotte because it is the kernel i have compiled, and the patch of my webcam is for this kernel 1107967754 M * Bertl okay, and what is the reason for using the old-style config on that? 1107967776 M * Bertl (i.e. the web.conf) 1107967795 M * marmotte because of the debian packages ? 1107967804 M * Bertl wrong answer! ;) 1107967821 M * marmotte joker ? ;-) 1107967824 M * Bertl I would understand if you said: 1107967846 M * Bertl because I have 20 servers configured with the old config, and I do not want to migrate to the newstyle config 1107967859 M * marmotte oh no, i start in vserver 1107967952 M * marmotte so i have to remove all the debian vserver packages, and install the source of the dev tools ? 1107968119 M * sod ok, I think the sane thing to do right now is build an identical test server and figure out a way to get things to work every time 1107968136 M * sod maybe even write a howto :) 1107968194 M * Bertl marmotte: yes, in this case, the _simplest_ way is to get a recent kernel 1107968206 M * Bertl 2.6.11-rc3 preferably 1107968228 M * Bertl patch it with a recent patch (1.9.4-rc5 for example) 1107968234 M * marmotte bouhouhou !! i have finished to compile mine 3 hours ago 1107968346 M * marmotte okay, i will do that 1107968356 M * Bertl which one did you compile? 1107968368 M * Bertl and do you still have the source/build tree? 1107968399 M * marmotte 2.6.10 1107968404 M * marmotte and yes 1107968408 M * Bertl with 1.9.3? 1107968433 M * marmotte patch-2.6.10-vs1.9.4-rc1.diff 1107968453 M * Bertl hmm, 3 hours ago, what was the reason for choosing rc1? 1107968494 A * Bertl is just trying to understand the linux-vserver user ... 1107968509 M * sod :) 1107968528 M * marmotte because i have checked if a new version exists 1107968544 M * Bertl aha ... where? 1107968549 M * marmotte i haven't checked sorry 1107968564 M * Bertl ah, okay, you found that one on your harddisk, right? 1107968578 M * marmotte right 1107968582 M * Bertl well, it's better than nothing ;) 1107968585 M * marmotte i feel guilty 1107968597 M * Bertl okay, you can use that one for now 1107968612 M * Bertl but upgrade to 1.9.4 once it is released 1107968614 M * marmotte thanks 1107968632 M * Bertl now for the tools, what tools/version do you ahve? 1107968639 M * Bertl the debian 0.30-whatever? 1107968656 M * marmotte util-vserver 0.30-14 1107968665 M * marmotte vserver-debian 0.1.9 Tools to manage debian virtual servers 1107968673 M * marmotte debian packages 1107968673 M * Bertl hehe, okay .. so be it ... 1107968676 M * marmotte for the moment 1107968714 M * Bertl in your case, you only need to work around the vproc issues 1107968730 M * Bertl but it is not easy with the old tools ... 1107968763 M * Bertl so if you do not have some kind of special sympathy for the stable tools I'd choose the devel tools 1107968842 M * Bertl somewhere, I jsut don't know where, are debian specific tools (0.30.196++) 1107968857 M * marmotte ok, i remove all the debian packages, and install the latest tools 1107968883 M * sod thank you guys, I'm going home now; be back later 1107968887 Q * sod Quit: I don't suffer from insanity, I enjoy every minute of it. 1107968908 M * Bertl http://www-user.tu-chemnitz.de/~ensc/util-vserver/alpha/util-vserver-0.30.203.tar.bz2 1107968953 M * marmotte thanks !! 1107969030 M * Bertl you're welcome! 1107969171 A * marmotte is reading the REAME of util-vserver-0.30.203 1107969317 M * Loki|muh oh, there are new utils 1107969879 Q * _are_ Quit: Disconnecting 1107969900 M * Bertl okay, folks, back later ... 1107969905 N * Bertl Bertl_oO 1107969951 A * marmotte disturbed for 15 min 1107970957 A * marmotte working on vservers tools 1107971015 J * sod ~sod@217.156.63.28 1107971833 Q * prae Remote host closed the connection 1107972260 M * marmotte Bertl_oO: thanks for your help, i'm going to stop for this evening. i will come later this week 1107972375 Q * marmotte Quit: Leaving 1107972958 M * micah I am curious how people manage their vservers, especially in an ISP-type environment 1107973014 M * micah I am wanting to use vservers to isolate "customers" (my customers are non-profit organizations actually), but I do not want to install separate apache/mysql etc. so see the benefit of unification. Additionally having some sort of "control panel" that can be used cross vservers seems very useful to me 1107973034 M * micah I am having trouble coming to grips with unification and how I can use that effectively 1107973043 M * micah so I am hoping others have tackled this and can give me some pointers 1107973936 Q * rs Quit: leaving 1107979490 Q * DaCa Ping timeout: 480 seconds 1107980149 N * Bertl_oO Bertl 1107980186 M * Bertl micah: sounds very typical ... 1107980196 M * Bertl evening folks! 1107980530 M * halorgium heh ... if only it was evening :) 1107981087 M * mugwump not long halorgium ... enjoy the sun 1107981116 J * Tbery ~tb@rt-pha-1.karneval.cz 1107981118 M * halorgium mmmm chch is good ... you? 1107981121 M * Tbery hi 1107981171 M * mugwump yeah it should be nice pretty much all over until full moon or so. it's hot here, I'm about to walk through some town belt to work 1107981538 M * Bertl okay, back later ... 1107981543 N * Bertl Bertl_oO 1107982872 J * Nupo user50@83.73.5.142.ip.tele2adsl.dk 1107982999 P * Nupo 1107984006 N * Bertl_oO Bertl 1107984020 M * Bertl hmm, okay, should be back for real now ;) 1107984051 J * _are_ ~are@dsl-084-056-138-045.arcor-ip.net 1107984067 M * _are_ hi 1107984083 M * Bertl welcome back _are_! 1107984619 Q * _are_ oxygen.oftc.net xenon.oftc.net 1107984619 Q * SiD3WiNDR oxygen.oftc.net xenon.oftc.net 1107984619 Q * click oxygen.oftc.net xenon.oftc.net 1107984619 Q * Snow-Man oxygen.oftc.net xenon.oftc.net 1107984619 Q * boklm oxygen.oftc.net xenon.oftc.net 1107984619 Q * BobR_oO oxygen.oftc.net xenon.oftc.net 1107984619 Q * micah oxygen.oftc.net xenon.oftc.net 1107984619 Q * switch oxygen.oftc.net xenon.oftc.net 1107984619 Q * Bertl oxygen.oftc.net xenon.oftc.net 1107984687 J * click click@dsl-84-161.aal.tiscali.no 1107984710 J * SiD3WiNDR luser@bastard-operator.from-hell.be 1107984744 T * services.oftc.net http://linux-vserver.org/ | latest stable 1.2.10, devel 1.9.{3,4-rc5}, ng8.13 -- He who asks a question is a fool for a minute; he who doesn't ask is a fool for a lifetime 1107984896 J * boklm boklm@woper.mars-attacks.org 1107984896 J * Bertl ~herbert@janus.mc.tuwien.ac.at 1107984896 T * unununium.oftc.net http://linux-vserver.org/ | latest stable 1.2.10, devel 1.9.{3,4-rc5}, ng8.13 -- He who asks a question is a fool for a minute; he who doesn't ask is a fool for a lifetime 1107985018 J * Snow-Man ~sfrost@snowman.net 1107985032 M * Bertl hmm, evening Snow-Man?! 1107985180 J * BobR_oO ~georg@MAIL.13thfloor.at 1107985181 J * micah micah@micha.hampshire.edu 1107985197 J * switch ~switch@61.206.115.5.user.ad.il24.net 1107985210 M * Bertl welcome switch?! 1107986071 M * boklm hello 1107986093 M * Bertl did I wake you? 1107986338 J * DaCa ~danny@mail.limehouse.org 1107986446 Q * ndim Ping timeout: 480 seconds 1107986489 J * Vantage ~Vantage@www.toddcharron.com 1107986511 M * Bertl welcome Vantage!? 1107986521 M * Vantage thanks 1107986531 M * Bertl ah, a real join, wasn't sure ;) 1107986541 M * Vantage heh, yup. i'm real... i think... 1107986542 M * Vantage :) 1107986564 M * Bertl so what brings you here? 1107986578 A * Bertl .o( hmm, probably some irc client ;) 1107986584 M * Vantage got a question about vserver and debian. i know woody's packages are out of date and not all that useful, but how about sarge/sid? any additional patches needed (or just use vanilla kernel) 1107986618 M * Vantage and by vanilla kernel i mean one from kernel.org and patch from the main site as opposed to using the debian patches/kernel 1107986623 M * Bertl give me numbers! what kernel version, what tools? 1107986636 M * Vantage right now i'm looking at 2.4.27 kernel 1107986639 M * Vantage with cx patch 1107986654 M * Vantage util-vserver 0.30 1107986657 M * Bertl okay, ctx patch is dead for more than one year now ;) 1107986667 M * Vantage ok, so that's not useful then ;) 1107986667 M * Bertl but 1.2.10 should be fine ... 1107986675 J * ndim U2FsdGVkX1@helena.bawue.de 1107986715 M * Vantage so grab vanilla source and patch with 1.2.10. are the tools ok? 1107986735 M * Vantage does 1.2.10 have quota support? disk limit or otherwise? 1107986823 J * _are_ ~are@dsl-084-056-138-045.arcor-ip.net 1107986994 M * Bertl nope, but there is a patch (q0.14) available 1107987020 M * Bertl util-vserver 0.30 is fine ... there is no newer AFAIK 1107987048 M * Bertl (of course you could also use the devel/alpha tools with 1.2.10) 1107987129 M * Vantage how stable is the alpha patches/utils? also, does the alpha patch include the quota patch or still need it applied separately? 1107987196 M * Vantage i managed to get a vserver set up using the debian tools and cx patch, however, i can't see any way of controlling the amount of disk space used by the virtual server (which is obviously not good) 1107987256 M * Bertl okay, first the quota patch is a kernel patch, so you need to apply that _in addition_ to the 1.2.10 patch ... 1107987287 M * Bertl then, it will requires some additional tools to control the settings 1107987296 M * Bertl (those are called quota tools) 1107987337 M * Bertl regardless if you use the stable tools (0.30) or the alpha tools (0.30.203) 1107987465 M * Vantage ah, ok. i was under the impression that newer versions of the tools and patches were going to include the quota patches and tools respectively 1107987474 M * Vantage thanks for clearing that up 1107987618 M * Bertl the thing is ... 2.6/1.9.x included the disk limits 1107987647 M * Bertl but, (and here is the important difference) there is no quota patch yet for 2.6/1.9.x 1107988251 Q * Tbery Ping timeout: 480 seconds 1107988711 J * chrish01 ~chrish01@69.90.131.25 1107988999 M * Bertl welcome chrish01! 1107989012 M * chrish01 afternoon Bertl 1107989043 M * Bertl it's still 30 minutes to midnight ;) 1107989061 M * chrish01 so im not wrong ... yet =P 1107989103 M * Bertl indeed *G* 1107990182 Q * chrish01 Quit: Leaving 1107991264 J * prae ~prae@sherpadown.net 1107991454 M * Bertl welcome prae! 1107991623 M * prae hi Bertl