1264204833 Q * harobed Ping timeout: 480 seconds 1264207329 Q * bonbons Quit: Leaving 1264207878 J * derjohn_mob ~aj@e180194181.adsl.alicedsl.de 1264208510 Q * fzylogic Quit: fzylogic 1264208981 Q * dowdle Remote host closed the connection 1264215648 J * derjohn_foo ~aj@e180195089.adsl.alicedsl.de 1264216078 Q * derjohn_mob Ping timeout: 480 seconds 1264217682 J * aj__ ~aj@e180195186.adsl.alicedsl.de 1264217878 Q * derjohn_foo Ping timeout: 480 seconds 1264219255 J * SauLus_ ~SauLus@c192145.adsl.hansenet.de 1264219255 Q * SauLus Read error: Connection reset by peer 1264219272 N * SauLus_ SauLus 1264228979 Q * balbir Read error: Connection reset by peer 1264231453 Q * nenolod Remote host closed the connection 1264232094 Q * watsonian Quit: watsonian 1264233258 J * balbir ~balbir@122.172.51.240 1264235177 J * hijacker_ ~hijacker@87-126-142-51.btc-net.bg 1264235756 J * barismetin ~barismeti@jua06-1-82-242-159-114.fbx.proxad.net 1264236794 J * nenolod ~nenolod@67.202.104.35 1264237818 Q * kjj Ping timeout: 480 seconds 1264239445 J * ghislain ~AQUEOS@adsl2.aqueos.com 1264239690 J * kjj ~kjj@pool-74-107-128-126.ptldor.fios.verizon.net 1264239706 Q * ghislain 1264239942 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d 1264244993 M * harry hmm.. about those bugs... Bertl_zZ , there could be another thing... it could be a mainline bug, that gets handled a little different if you use vserver or grsec 1264245032 M * harry anyway, for now, i would definately suggest grsec users to disable REFCOUNT check in kernel, since i'm quite positive i haven't fixed all possible problems yet... 1264245054 M * harry (i do have an idea on the random kills in grsec tough...)_ 1264245063 M * harry that's related to the refcount problem 1264245072 M * harry so that might be a first test 1264245960 J * pmenier ~pmenier@ACaen-152-1-2-26.w83-115.abo.wanadoo.fr 1264246488 J * SubZero ~SubZero@chello089076140236.chello.pl 1264248881 Q * barismetin Remote host closed the connection 1264249168 N * Bertl_zZ Bertl 1264249172 M * Bertl morning folks! 1264249207 J * petit ~chatzilla@abbadingo.shayol.org 1264249253 M * petit Hi 1264249295 M * petit I have 2 debian etch server with about 5 or 6 vserver (debian etch or lenny) on it 1264249322 M * petit is there an how to upgrade ? 1264249337 M * petit I wnat to upgrade the real computer to debian lenny 1264249348 M * petit and the vserver from etch to lenny 1264249374 M * petit I try to upgrade a vserver guest to lenny with the debian way 1264249398 M * petit by changing /etc/apt-/sources.list and apt-get update/dist-upgrade with no luck 1264249441 M * petit So now I think I must upgrade the real computer and réinstall from scratch the guests :-( 1264249464 M * petit do you know an easy way ? 1264249663 M * Bertl first, to the nomenclature, we call the isolated entities guests (makes it simple to tell them apart from the host :) 1264249696 M * Bertl second, the guest itself is independant from the host, i.e. you can easily run a newer debian version in a guest than the host has installed 1264250037 M * petit Yes, I do it with a guest debian lenny on a debian etch host 1264250105 M * petit my problem is how to upgrade the etch guests to lenny. If I do a standard upgrade in a guest 1264250149 M * petit it install a new kernel (in the guest !), klogd, initramfs, ... what I don't want in the guest 1264250186 M * petit My plan was to upgrade the guests and when all the guest will be in lenny, to upgrade the host 1264250207 M * petit but I don't know how to upgrade a guest :-) (or :-( ) 1264250214 M * Bertl well, that's more a debian upgrade issue (that it wants to install all kind of useless stuff :) as I see it, you have a few options there 1264250329 M * Bertl 1) you can create a 'new' guest with util-vserver and copy the config/user data over 1264250364 M * Bertl 2) you can upgrade the guest 'the debian way' and run the cleanup scripts over that (and probably clean up some packages manually) 1264250408 M * Bertl 3) you only update the packages, i.e. use e.g. externalized package management to install the same packages you already have installed, but from the new release 1264251131 M * petit ok 1264251147 M * petit I will try this. thanks for the ideas. 1264251636 M * Bertl np 1264251921 M * harry Bertl: you have any ideas on those OOM errors? 1264251983 M * Bertl not yet, all I see is that a signal seems to be ignored, and the OOM condition continues forever (unclear is why) but to me it looks like a mainline issue for now ... 1264252046 M * harry think so too 1264252066 M * harry but... it still is a bitch to crack... 1264252073 M * harry and quite important for vserver users... 1264252185 Q * bonbons Quit: Leaving 1264253102 Q * petit Ping timeout: 480 seconds 1264253280 Q * hijacker_ Quit: Leaving 1264256115 Q * Medivh Ping timeout: 480 seconds 1264256316 J * petit ~chatzilla@abbadingo.shayol.org 1264256811 Q * pmenier Quit: Konversation terminated! 1264259008 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d 1264259247 Q * petit Ping timeout: 480 seconds 1264259610 J * petit ~chatzilla@abbadingo.shayol.org 1264259688 Q * petit 1264264411 N * SubZero Guest372 1264264411 J * SubZero` ~SubZero@chello089076140236.chello.pl 1264264412 N * SubZero` SubZero 1264264492 J * hijacker_ ~hijacker@87-126-142-51.btc-net.bg 1264264841 Q * Guest372 Ping timeout: 480 seconds 1264266044 Q * hijacker_ Remote host closed the connection 1264266163 J * {DRagON} ~lm@krasnet-gprs.etk.ru 1264267188 Q * {DRagON} Quit: Neon script òèïà :) ãã (http://irc-rulez.h2m.ru) 1264267447 J * barismetin ~barismeti@jua06-1-82-242-159-114.fbx.proxad.net 1264268222 Q * SubZero 1264268762 Q * aj__ Ping timeout: 480 seconds 1264269899 Q * barismetin Remote host closed the connection 1264271021 Q * geos_one Quit: ChatZilla 0.9.86 [Firefox 3.6/20100120013823] 1264271109 J * geos_one ~chatzilla@chello084115149052.4.graz.surfer.at 1264274116 Q * geos_one Quit: ChatZilla 0.9.86 [Firefox 3.6/20100123190657] 1264275799 J * geos_one ~chatzilla@chello084115149052.4.graz.surfer.at 1264276343 J * ktwilight_ ~keliew@148.80-240-81.adsl-dyn.isp.belgacom.be 1264276343 Q * ktwilight Read error: Connection reset by peer 1264277707 N * balbir bsarora 1264277761 N * bsarora balbir 1264277990 J * aj__ ~aj@p5B23CE56.dip.t-dialin.net 1264278608 J * petit ~chatzilla@abbadingo.shayol.org 1264279360 J * yarihm ~yarihm@80-219-171-55.dclient.hispeed.ch 1264279584 Q * bonbons Quit: Leaving 1264280898 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d 1264284207 J * Felipe_McMont ~fmc@187.59.244.150 1264284483 Q * geos_one Ping timeout: 480 seconds 1264285973 Q * Felipe_McMont Remote host closed the connection 1264286900 Q * balbir Ping timeout: 480 seconds 1264286963 Q * aj__ Ping timeout: 480 seconds 1264287555 J * balbir ~balbir@122.172.62.45 1264290329 J * derjohn_mob ~aj@e180195186.adsl.alicedsl.de 1264290950 Q * NOC|YEP Ping timeout: 480 seconds 1264291083 Q * bonbons Quit: Leaving