1185151785 J * DoberMann_ ~james@AToulouse-156-1-69-174.w90-16.abo.wanadoo.fr 1185151895 Q * DoberMann[ZZZzzz] Ping timeout: 480 seconds 1185153529 J * Solaris ~satan@85.138.105.7 1185153949 A * Supaplex pushes Solaris's buttons until ... oops, it crashed. 1185153954 M * Supaplex my bad 1185154004 M * Solaris whats that? 1185154016 M * Solaris crash? i dont no the meaning of that word.. 1185154056 M * Supaplex it's like when you drop a window 1185154064 M * Supaplex ;) hehe 1185154065 M * Solaris must be some kind of windows terminology 1185155288 Q * bzed Quit: Leaving 1185156830 Q * nou Ping timeout: 480 seconds 1185157472 J * nou Chaton@causse.larzac.fr.eu.org 1185157729 M * onox silly Solaris :p 1185157746 M * onox linux programs can crash too :) 1185158535 Q * nou Ping timeout: 480 seconds 1185158762 J * nou Chaton@causse.larzac.fr.eu.org 1185160323 Q * onox Quit: leaving 1185161606 Q * gerrit_ Quit: Client exiting 1185161674 Q * arachnist Quit: bbl 1185163374 J * Hollow_ ~hollow@proteus.croup.de 1185163374 Q * Hollow Read error: Connection reset by peer 1185163379 N * Hollow_ Hollow 1185165062 J * meandtheshell ~markus@85.127.114.21 1185168579 Q * blues Read error: Connection reset by peer 1185169585 Q * meandtheshell Quit: Leaving. 1185169871 J * meandtheshell ~markus@85.127.102.246 1185169898 J * balbir ~balbir@122.167.3.244 1185171445 N * DoberMann_ DoberMann[PullA] 1185171462 Q * nou Ping timeout: 480 seconds 1185172310 J * sharkjaw ~gab@158.36.44.106 1185173249 J * dna ~naucki@104-222-dsl.kielnet.net 1185173824 J * nou Chaton@causse.larzac.fr.eu.org 1185174383 Q * Aiken Remote host closed the connection 1185174762 J * FireEgl FireEgl@Sebastian.Tcldrop.Com 1185175094 Q * sharkjaw Ping timeout: 480 seconds 1185175248 J * ktwilight_ ~ktwilight@253.197-66-87.adsl-static.isp.belgacom.be 1185175520 M * matti Morning. 1185175609 Q * ktwilight Read error: Connection reset by peer 1185175841 J * Aiken ~james@ppp121-45-220-241.lns2.bne1.internode.on.net 1185177496 Q * AStorm Quit: Bye, and thanks for all the fish 1185177995 Q * virtuoso Ping timeout: 480 seconds 1185178157 J * AStorm ~astralsto@host-81-190-179-124.gorzow.mm.pl 1185178473 Q * AStorm Quit: Bye, and thanks for all the fish 1185179305 J * pmenier ~pmenier@LNeuilly-152-22-72-5.w193-251.abo.wanadoo.fr 1185181525 J * ManaPirat ~cst@stamper.dp-media.de 1185181552 M * ManaPirat hi :-) 1185181646 M * ManaPirat this question maybe allows for subjective answers only, but which distribution do you think supports linux-vserver the best? 1185181693 M * ManaPirat i am looking forward to set it up on an old IBM-Server today and i am not sure if gentoo, on that i used linux-vserver verry successfull over thelast 2 years, is the right choice 1185181719 M * sid3windr if it's less than 16GHz gentoo probably isn't the right choice? *SCNR* 1185181729 M * ManaPirat bugger :P 1185181744 M * ManaPirat c'mon the compiling isnt what hurts :-) 1185181753 M * ManaPirat lets nmot start a flame *g* 1185181766 M * sid3windr :D 1185181786 M * sid3windr are you the one who is going to maintain the machine? 1185181793 M * ManaPirat for sure 1185181801 M * sid3windr then I'd say go with what you know best? 1185181802 M * ManaPirat but maybe not the vserver-quests 1185181826 M * ManaPirat i know gentoo best, but the current state of vserver there is .. uhm not so transparent to me, you know what i mean? 1185181841 M * ManaPirat alot of things changed and the guys in #gentoovserver are verry verry idle 1185181858 M * sid3windr ah 1185181863 M * sid3windr well, don't know about that 1185181876 M * ManaPirat its ok :-). What do you use? Debian? 1185181876 M * sid3windr I use debian and it works (but you need to upgrade the utils to a newer version for full comfort) 1185181887 M * sid3windr own kernel compiles though, not debian-supplied 1185181910 M * ManaPirat and could you use debian as vserver-host and install gentoo-vserver guests using a gentoo-stage? 1185181930 M * ManaPirat hehe ok sorry somewhat gentoo-specific ;) 1185181965 M * ManaPirat ah btw: is the vserver-migration now better supported using the utils? 1185182068 M * sid3windr I'd think you can run any linux distro as guest of any host 1185182074 M * sid3windr only the installation of it may be difficult 1185182080 M * sid3windr but once you have a tarball it should run fine 1185182084 M * sid3windr no idea about migration 1185182148 M * ManaPirat okay :-) thanks 1185182165 A * ManaPirat awaits maybe further comments and fetches new coffee 1185182476 M * renihs ManaPirat, as long as the guest distro doesnt expect a specific (patched?) kernel eveything should be fine 1185182485 J * cedric ~cedric@80.70.39.67 1185182493 M * renihs since they all guests "share" the kernel of the host 1185182612 M * ManaPirat i understand renihs :-) 1185182618 M * ManaPirat and know what, i remember you :) 1185182628 M * sid3windr ohnoes 1185182636 M * ManaPirat you helped me out with a vserver-iptables NAT thingy 2 yars ago or so :D 1185182806 M * renihs hmm possible :p 1185182820 M * renihs my brain isnt that accurate for such long term memories :p 1185183102 M * ManaPirat ;) 1185183182 M * Hollow ManaPirat: well, baselayout-2 is very usable right now, although it's still alpha4 1185183183 M * ManaPirat renihs can you tell me how good vserver-migration, hot / cold replacement of vserver-guests works currently? 1185183203 M * ManaPirat ah Hollow so you mean keywording it might not hurt? 1185183223 M * renihs Hollow, ya i am switching to it since friday 1185183233 M * renihs seems to be going fine :p 1185183246 M * Hollow not at all, i run all my guests with baselayout-2 already... there are still some cosmetic bugs, and you may need to keyword some other packages because of new init scripts, but it works fine for me :) 1185183253 M * ManaPirat well the firsz machine i setup will be for testing purpose, but the developers that will use it would be happy if it wouldn't be thaaat unstable *g* 1185183290 M * ManaPirat aah nice so i got thwo good experiances ;) .. 1185183302 M * Hollow unfortunately we don't have the time to keep the old baselayout-vserver up to date, but there are already plans regarding to stabilize baselayout-2 for 2007.1 1185183302 M * ManaPirat thanks guys- ill stick to linux-vserver (and this channel for soem time) 1185183322 M * ManaPirat yes Hollow i read a blog entry .. ah wait its YOUR blog entry :D 1185183328 M * Hollow :) 1185183343 M * ManaPirat hehe a "PITA" i like this word 1185183357 M * ManaPirat so your working on this stabalisation since November? o.O 1185183363 M * ManaPirat alot of work huh? 1185183372 M * ManaPirat stabilisation *grmpf* 1185183419 M * Hollow it is a lot of work to keep baselayout-vserver in sync.. but it wasn't that much work to get baselayout-2 working with vservers.. but since baselayout-2 is a complete rewrite we have to be careful regarding stabilization 1185183558 M * Hollow daniel_hozac: btw, the weird characters issue seems to be solved with alpha4 and our env fix for TERM 1185183591 M * ManaPirat i understand you Hollow :) 1185183596 M * ManaPirat i'll try it 1185183644 M * Hollow ManaPirat: if you start with a fresh (guest) installation it will work out-of-the-box, but upgrading from baselayout-1 to baselayout-2 is not yet smooth enough :) 1185183663 M * ManaPirat no, - no upgrades ;) 1185183667 M * Hollow in fact, if you forget to add some new init scripts, your system might not boot at all ;) 1185183688 M * ManaPirat *g* i know why i did not update my vserver-host the last year 1185183691 M * Hollow (if you use lvm, e.g.) 1185183699 M * ManaPirat *g* well yes it uses lvm 1185183709 M * Hollow hehe 1185183724 M * Hollow then be warned that you need to add the device-mapper init script to the boot runlevel 1185183729 M * Hollow otherwise you will be fcked :P 1185183732 M * ManaPirat thanks for the tipps, i'll be careful - and bug when things fail *grinevil* 1185183745 M * ManaPirat na, no lvm this time 1185183755 M * ManaPirat i#d stick to KISS 1185183771 M * Hollow feel free to ping me, i'm not looking at irc all the day :) 1185183834 M * ManaPirat glass-clear - if i don't you will now that you and the vserver-team did a good job :-) 1185183838 M * ManaPirat know 1185183841 M * sid3windr ping Hollow 1185183842 M * sid3windr :> 1185183848 A * Hollow stabs sid3windr :P 1185183852 M * sid3windr :( 1185183857 M * Hollow aw. sorry hun 1185183859 M * ManaPirat *g* 1185183861 M * sid3windr :) 1185185191 J * DavidS ~david@85.125.165.34 1185185720 J * chand ~chand@212.99.51.254 1185185801 A * ManaPirat lunchtime 1185186721 J * virtuoso ~s0t0na@80.253.205.251 1185187126 J * bzed ~bzed@dslb-084-059-110-198.pools.arcor-ip.net 1185190110 Q * DavidS Quit: Leaving. 1185191124 M * daniel_hozac Hollow: okay... do we know what caused it yet? 1185191265 M * Hollow daniel_hozac: no :) 1185191375 Q * zLinux Ping timeout: 480 seconds 1185191377 Q * FireEgl Quit: Bye... 1185191450 M * daniel_hozac hehe, okay. 1185192107 J * AStorm ~astralsto@host-81-190-179-124.gorzow.mm.pl 1185192191 M * Bertl_oO okay .. off to bed now ... have a good one everyone! 1185192198 N * Bertl_oO Bertl_zZ 1185192562 M * renihs good night 1185192570 M * renihs erm, good sleep 1185192571 M * renihs :p 1185192632 Q * Aiken Quit: Leaving 1185192876 J * Piet ~piet@tor.noreply.org 1185193459 N * BobR_zZ BobR 1185193478 N * BobR BobR_afk 1185194330 M * ManaPirat *g* 1185194550 Q * meandtheshell Quit: Leaving. 1185194882 J * meandtheshell ~markus@85.127.104.34 1185195749 J * ema ~ema@rtfm.galliera.it 1185198089 N * WorkRoey Roey 1185198957 J * FireEgl FireEgl@4.0.0.0.1.0.0.0.c.d.4.8.0.c.5.0.1.0.0.2.ip6.arpa 1185198981 M * renihs hmm are there plans for vserver to be incorporaed in main kernel and if anytime soon? or predictable? 1185199073 M * daniel_hozac Linux-VServer as-is will never be incorporated. 1185199093 M * daniel_hozac bits and pieces (though not the exact implementation) are slowly being merged though. 1185199150 M * harry what's the reason? 1185199156 M * daniel_hozac for what? 1185199193 M * harry for no integration in the mainline kernel 1185199221 Q * FireEgl Read error: Connection reset by peer 1185199235 M * harry and: why not the exact implemetation, what's wrong with the vserver implementation according to the mainline kernel developers? 1185199261 M * renihs daniel_hozac, mkay :p 1185199268 M * renihs i was remembering it that way but wasnt sure 1185199340 M * mjt i wonder. Is it ever possible to do something like switch_root in a single, non-main namespace? 1185199390 M * mjt currently for vserver guest, one has to mount /vservers/$foo, but root directory on the host remains mounted too. I wonder if there's a way to replace it completely. 1185199421 M * daniel_hozac harry: because Bertl's only one man, pushing things like this to mainline isn't easy... also, mainline wants the "generic" building blocks, not complete solutions. 1185199443 M * harry true :) 1185199573 J * friendly12345 ~benj@ppp59-167-144-7.lns4.mel6.internode.on.net 1185199581 M * harry daniel_hozac: what's the way to install rhel on vserver guests? 1185199601 M * daniel_hozac vserver ... build -m yum ... -- -d centos5 1185199627 M * harry not centos 1185199630 M * harry i need RHEL 1185199684 M * friendly12345 daniel_hozac: this question was probably asked 30 seconds ago but I must ask it again: 1185199778 M * friendly12345 daniel_hozac: is there any chance of vserver sources being merged into the mainline kernel? If not, can you direct me to the appropriate list discussion/docs 1185199803 M * harry 15:57 < daniel_hozac> Linux-VServer as-is will never be incorporated. 1185199803 M * harry 15:58 < daniel_hozac> bits and pieces (though not the exact implementation) are slowly being merged though. 1185199810 M * harry 16:03 < daniel_hozac> harry: because Bertl's only one man, pushing things like this to mainline isn't easy... also, mainline wants the "generic" building blocks, not complete solutions. 1185199817 M * harry there you go 1185199851 M * friendly12345 harry: thank a lot 1185199856 M * friendly12345 harry: *thanks 1185199856 M * harry np 1185199897 M * mjt lol 1185200016 M * mjt by the way - those building blocks which are being incorporated slowly - guess it means more API changes. 1185200033 M * mjt (which is already a large mess) 1185200097 M * mjt what's the reason of using uint_least64_t fields in structs and parameters and converting them to uint64_t when communicating with the kernel? Why not use uint64_t directly? 1185200098 M * daniel_hozac harry: CentOS is RHEL, just rebuilt. 1185200116 M * mjt i mean util-vserver library stuff 1185200133 M * harry daniel_hozac: so.... 1185200137 M * harry i need RHEL 1185200138 M * daniel_hozac harry: so just take the centos5 distro, point it at your RHEL CDs/repo, build. 1185200140 M * harry not cenots 1185200146 M * harry aha 1185200157 M * harry management here says: 1 distro 1185200160 M * harry so it's RHEL 1185200162 M * friendly12345 mjt: yes, I understand 1185200181 M * daniel_hozac mjt: you'd have to ask ensc :) 1185200182 M * harry we need rh for oracle/blackboard/ess/ds8000/... support 1185200184 M * mjt note that on e.g. i386 uint64_t is the same as uint_least64_t - so that no conversion is necessary at all. I wonder if there's such an arch which uint_least64_t is larger than uint64_t... 1185200204 M * harry i know it's binary compatible... but management says: 1 1185200204 M * daniel_hozac mjt: yep. 1185200209 M * friendly12345 mjt: probably the most asked question, around here, especially given the recent xen merges etc 1185200214 M * harry and centos and rh = 2 :) 1185200245 M * mjt ensc: ping? :) (as suggested... ;) 1185200253 M * daniel_hozac friendly12345: why would it be? would've made more sense due to the user namespace merge... 1185200318 M * mjt xen is very different from vserver. xen does not touch many things in kernel, while vserver (and virtuozzo/openvz) is ALOT of changes all over. 1185200352 M * harry "a lot" 1185200400 M * mjt xen only touches the very low-level (like just another arch), ditto for lguest. While vserver changes all the kernel core - filesystems, permissions, schedulers etc yadda 1185200456 M * friendly12345 mjt: yes, sounds like a bit of work 1185200607 M * daniel_hozac mjt: btw, adding another namespace in the kernel doesn't mean any API-changes at all. 1185200635 M * daniel_hozac mjt: we actually did stop to think about that when we added support for the first two (uts and IPC) ;) 1185200780 M * mjt hmm? 1185200817 M * mjt so vserver patch will add its own things ignoring whatever will be in kernel? Or it will be a 'compatibility layer'? 1185200824 M * daniel_hozac there's a reason vc_enter_space accepts a bitmask of spaces to enter... 1185200846 M * daniel_hozac we've been using the uts and IPC spaces since they first appeared in the kernel. 1185200858 M * daniel_hozac i expect the same to happen with any other space. 1185200862 M * mjt heh. I wondereed what's the difference between vc_enter_space and vc_enter_space_v0 but didn't bother to look yet ;) 1185200985 Q * Piet Ping timeout: 480 seconds 1185201205 P * friendly12345 1185201485 J * onox ~onox@kalfjeslab.demon.nl 1185202339 M * mjt if i enter an already existing {network,process}context, using --migrate option of [nv]context, is it still necessary to set the context's properties (like using naddress, or vuname/vattribute etc) ? 1185202428 M * daniel_hozac no. 1185202499 M * mjt so `vserver $foo enter' becomes just -- nice .. exec-ulimits ... ncontext --migrate .. vcontext --migrate 1185202503 M * mjt ? 1185202526 M * daniel_hozac for enter you'll want --vlogin to vcontext as well. 1185202552 M * mjt or just exec.. whatever 1185202572 M * mjt i mean all the rest - like chbind (naddress) etc - which are unnecessary 1185202689 M * daniel_hozac chbind will just migrate if the context exists. 1185202776 M * mjt hmm... how to kill a persistent context? :) 1185202844 M * daniel_hozac remove the persistent bit. vserver.stop does it... 1185202862 M * mjt blah. How simple. I'm stupid ;) 1185205065 J * FireEgl FireEgl@2001:5c0:84dc:1:4:: 1185205373 J * stefani ~stefani@tsipoor.banerian.org 1185205930 J * DavidS ~david@85.125.165.34 1185205952 Q * DavidS Remote host closed the connection 1185206251 J * DavidS ~david@85.125.165.34 1185206544 N * ensc Guest72 1185206554 J * ensc ~irc-ensc@p54B4E423.dip.t-dialin.net 1185206600 M * AStorm Ok guys, there's 2.6.23-rc1 out 1185206609 M * AStorm begin porting VServer patch, please :-) 1185206665 Q * Guest72 Ping timeout: 480 seconds 1185207229 Q * DavidS Ping timeout: 480 seconds 1185207254 Q * ManaPirat Remote host closed the connection 1185208026 Q * Hollow Quit: Disconnecting from stoned server. 1185208039 J * Hollow ~hollow@proteus.croup.de 1185209170 M * daniel_hozac AStorm: calm down, final won't be out for another month or so... 1185209199 M * AStorm That's why I said "begin", not "do it right now" 1185209208 M * AStorm because that will be a lot of work 1185209224 M * AStorm (unlike 2.6.21 vs 2.6.22) 1185209345 M * daniel_hozac how about 2.6.18->2.6.19? 1185209390 M * daniel_hozac (i.e. compare apples and apples, not apples and oranges) 1185209441 M * AStorm hmm, that was a bit of work, but still, I think current one will be harder (if you are to port it properly, not just bump a bit) 1185209495 M * daniel_hozac sure, changing the scheduler always complicates matters. 1185209763 M * AStorm bonus points if you manage to use user_namespaces 1185209790 Q * pmenier Quit: pmenier 1185209995 M * daniel_hozac shouldn't be a problem at all. why would it? 1185210005 M * AStorm I tried and failed. 1185210021 M * AStorm Probably messed up something :> 1185210056 M * daniel_hozac i wasn't aware they were merged already though. 1185210079 M * daniel_hozac actually, the containers roadmap of friday had that on it. 1185210371 Q * ema Quit: leaving 1185211201 J * emtt1 ~eric@dynamic-acs-24-154-91-152.zoominternet.net 1185211309 N * DoberMann[PullA] DoberMann 1185212517 Q * cedric Quit: cedric 1185213767 M * mjt what's user_namespaces? 1185213809 M * mjt ummm... rtfm 1185215045 J * duckx ~Duck@tox.dyndns.org 1185215105 Q * chand Ping timeout: 480 seconds 1185217306 Q * FireEgl Read error: Connection reset by peer 1185218253 J * FireEgl FireEgl@Sebastian.FireEgl.Com 1185219854 J * zLinux ~zLinux@88.213.10.216 1185220130 Q * zLinux Remote host closed the connection 1185221360 J * jescheng ~jescheng@proxy-sjc-2.cisco.com 1185221532 M * jescheng hello 1185221550 M * daniel_hozac hi 1185221573 M * jescheng hi , question on assigning ip addresses to vserver 1185221585 M * jescheng is there a way to assign ip address without having to restart the vserver? 1185221656 M * daniel_hozac sure. 1185221671 M * daniel_hozac naddress --nid --add --ip / 1185221689 M * daniel_hozac (after actually adding the IP address to the host with e.g. ip addr add) 1185221772 M * daniel_hozac or well, the order doesn't matter. you'll have to do both though. 1185221890 M * jescheng ok , thanks. let me give it a try. 1185222303 P * stefani I'm Parting (the water) 1185222439 M * jescheng hi daniel, is "naddress" a command to run in linux? 1185222461 M * jescheng or should i run it in vserver? 1185222462 M * daniel_hozac if you have at least util-vserver 0.30.21... 2? 1185222469 M * daniel_hozac you have to run it on the host. 1185222674 M * jescheng no luck .. i have util-vserver-0.30.210 1185222795 M * jescheng is it not supported in .210? 1185222813 M * daniel_hozac no. 1185222818 M * daniel_hozac you'll have to restart the guest. 1185222976 Q * meandtheshell Quit: Leaving. 1185223140 M * jescheng ouch.. ok 1185223165 M * Supaplex humm what should I do with my 31 node 18,600 bogomips cluster 1185223176 M * jescheng thanks daniel 1185224941 J * dragonheart ~dragonhea@ppp59-167-41-164.lns2.cbr1.internode.on.net 1185225066 J * Aiken ~james@ppp121-45-220-241.lns2.bne1.internode.on.net 1185225096 M * jescheng is util-vserver-0.30.212 compatible with vserver kernel 2.6.14 patch version 2.0 ? 1185225109 M * daniel_hozac yes. 1185225120 M * daniel_hozac you'll want 0.30.213 though. 1185225235 M * jescheng oh ok, btw do you think there's any other way around this without having to upgrade... it might not be an option for us 1185225285 M * daniel_hozac well, i'm not entirely sure your kernel even supports this... 1185225296 M * daniel_hozac i think it should, but i don't know. 1185225323 M * jescheng oh..so it might not even compatible with .213? 1185225340 M * daniel_hozac the utils are massively backwards-compatible. 1185225372 M * daniel_hozac if you configure them right, you can run them on kernels with the initial versions of Linux-VServer (before it was called that) 1185225386 M * daniel_hozac or at least, that's the idea. 1185225450 M * jescheng oh ok - guess we'll have to try it out and see. 1185225548 M * daniel_hozac an upgraded kernel wouldn't be a bad idea though ;) 1185225649 Q * wenchien Ping timeout: 480 seconds 1185225726 M * jescheng yea...but unfortunately we don't have that option right now :) it always get some people nervous 1185225828 M * dragonheart great work vserver people. love how easy it is to work with. didn't take long to get started :-) 1185225849 M * daniel_hozac it shouldn't be hard ) 1185225851 M * daniel_hozac +: 1185225951 M * dragonheart shoudn't - if i didn't try to put the guest on a totally differnent network it would of taken me 1/2 the time :). thanks 1185226188 N * DoberMann DoberMann[ZZZzzz] 1185226399 J * chand ~chand@m167.net81-64-156.noos.fr 1185226412 Q * duckx Remote host closed the connection 1185226500 J * bonbons ~bonbons@ip-83-134-132-127.dsl.scarlet.be 1185226603 Q * onox Quit: leaving 1185226626 J * onox ~onox@kalfjeslab.demon.nl 1185227086 M * waldi bah, sparc is fun. i can kill a 2.6.22 within minutes 1185227102 M * daniel_hozac hehe. how? 1185227150 M * waldi kernel build 1185227156 M * waldi maybe pid overrun 1185227172 M * daniel_hozac neat. 1185227184 M * waldi it dies after between 2 and 5 minutes of a make -j16 run 1185227193 M * daniel_hozac any trace, or just sudden death? 1185227208 M * waldi just dead 1185227215 M * waldi nothing on the console 1185227253 M * daniel_hozac that's bad. 1185227273 M * waldi kernels up to .22 produces unkillable processes with nptl-glibc 1185227306 M * daniel_hozac on non-VServer too? 1185227311 M * waldi yes 1185227542 A * mnemoc happy to be at 2.6.21.6 1185227566 M * daniel_hozac you're probably not on sparc though :) 1185227574 M * mnemoc :) 1185227625 A * waldi goes back to 2.6.21 ... 1185227650 Q * chand Read error: Connection reset by peer 1185227651 J * chand ~chand@m167.net81-64-156.noos.fr 1185227848 M * AStorm waldi, is 2.6.23-rc1 affected too? 1185227891 M * waldi no idea 1185228053 M * waldi the .22 problem may be vserver specific ... 1185228411 J * chand_ ~chand@m167.net81-64-156.noos.fr 1185228411 Q * chand Read error: Connection reset by peer 1185228473 Q * bonbons Quit: Leaving 1185228493 Q * dna Quit: Verlassend 1185228894 M * bzed daniel_hozac: if I ssh to a machine, use vserver enter and kill the ssh connection hard then, the login process in the entered vserver eats 99% cpu and keeps running. that's no so nice 1185228911 M * daniel_hozac bzed: with 0.30.213? 1185228939 M * bzed 0.30.212 1185228943 M * daniel_hozac so, upgrade 1185228958 M * bzed let's see if there's a debian package yet 1185228962 M * daniel_hozac there is. 1185228987 M * daniel_hozac has been for weeks, if not months already. 1185229092 M * bzed yeah, just need to backport it to etch 1185229109 M * daniel_hozac i was referring to the backport. 1185229145 M * bzed on bpo? 1185229150 M * bzed I've finished my own in a second 1185229162 M * daniel_hozac yes. 1185229281 Q * chand_ Quit: chand_ 1185229314 Q * emtt1 Ping timeout: 480 seconds 1185229336 M * bzed daniel_hozac: cool that seems to have it fixed - thanks :) 1185229386 M * daniel_hozac you're welcome :) 1185229564 J * er ~sapan@pool-71-168-231-115.cmdnnj.fios.verizon.net 1185229591 P * er 1185231154 Q * FireEgl Quit: Bye... 1185232438 J * FireEgl FireEgl@Sebastian.FireEgl.Com 1185232796 J * phedny_ ~mark@ip56538143.direct-adsl.nl 1185233196 Q * phedny Ping timeout: 480 seconds 1185233578 Q * onox Quit: reboot