1220745685 J * quasisane ~sanep@c-75-68-62-13.hsd1.nh.comcast.net
1220746451 J * oliwel_ ~chatzilla@ppp-88-217-14-251.dynamic.mnet-online.de
1220746688 Q * oliwel Read error: Connection reset by peer
1220746703 N * oliwel_ oliwel
1220747222 J * ntrs ~ntrs@77.29.79.125
1220747706 Q * ntrs Ping timeout: 480 seconds
1220751042 J * jsambrook ~jsambrook@aelfric.plus.com
1220752101 Q * yarihm Quit: Leaving
1220753329 M * daniel_hozac oliwel: filesystems relying on umount for proper operation are broken.
1220754849 Q * androsch Read error: Connection reset by peer
1220758674 Q * derjohn_foo Ping timeout: 480 seconds
1220761217 Q * kiorky_ Ping timeout: 480 seconds
1220762058 J * kiorky ~kiorky@cryptelium.net
1220765416 J * ntrs ~ntrs@77.29.77.145
1220770510 J * balbir_ ~balbir@12.168.228.200
1220771547 J * derjohn_mob ~aj@e180205209.adsl.alicedsl.de
1220772298 Q * pisco Ping timeout: 480 seconds
1220772742 J * pisco ~pisco@tor.noreply.org
1220773014 N * Bertl_zZ Bertl
1220773019 M * Bertl morning folks!
1220774262 J * loddafnir ~mike@chello080108111137.5.11.univie.teleweb.at
1220776842 P * jsambrook 
1220777079 M * oliwel Bertl: Morning....
1220777168 N * DoberMann[ZZZzzz] DoberMann
1220778030 Q * ntrs Ping timeout: 480 seconds
1220778587 J * SlackLnx ~Lee@bl7-137-8.dsl.telepac.pt
1220782217 J * xdr ~xdr@4-173-96-87.cust.blixtvik.se
1220783293 Q * oliwel Quit: ChatZilla 0.9.83 [Firefox 3.0.1/2008070206]
1220783384 J * dennis ~dennis@dslb-084-059-217-038.pools.arcor-ip.net
1220783530 Q * dennis Remote host closed the connection
1220786653 M * Bertl okay, off for now ... bbl
1220786659 N * Bertl Bertl_oO
1220787007 M * sid3windr vxW: [»ps«,10709:#10001|10001|0] did lookup hidden ffff810079fb64b0[#0,2] »/dev/pts/0«.
1220787011 M * sid3windr what be this? :/
1220787368 M * daniel_hozac you're using older utils on a recent kernel and ran ps from a vserver ... enter shell.
1220787428 M * daniel_hozac (it's still going to appear with recent utils)
1220788782 M * sid3windr ahh
1220788786 M * sid3windr yea, that's very possible =)
1220788787 M * sid3windr thanks
1220788802 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d
1220788807 M * sid3windr I was trying to debug some failing stuff but apparently my disk was just full ;(
1220789908 Q * pisco Remote host closed the connection
1220790236 Q * Aiken Remote host closed the connection
1220790283 J * pisco_ ~pisco@tor.noreply.org
1220791953 J * ntrs ~ntrs@77.29.194.202
1220796821 N * ensc Guest5748
1220796821 Q * Guest5748 Remote host closed the connection
1220796831 J * ensc ~irc-ensc@77.235.182.26
1220797097 J * larsivi ~larsivi@169.80-202-217.nextgentel.com
1220797432 J * vargadani ~vargadani@catv-89-135-16-217.catv.broadband.hu
1220797541 M * vargadani hey there... is there a special way how vserver handles 127.0.0.1?
1220797561 M * daniel_hozac yes.
1220797669 M * vargadani thank you ^_^ 
1220797764 J * ntrs_ ~ntrs@77.29.194.202
1220797911 Q * ntrs Read error: Connection reset by peer
1220798688 Q * ntrs_ Ping timeout: 480 seconds
1220805325 M * vargadani there was somebody who had a Ubuntu 8.04 install and used a backport kernel from Etch I believe...
1220805344 M * vargadani i only know how to recompile the kernel and use that one
1220805363 M * vargadani can sb give me some more info on alternate ways of getting ubuntu run with vserver?
1220805749 J * blues blues@ada117.neoplus.adsl.tpnet.pl
1220805867 Q * blues_ Ping timeout: 480 seconds
1220806507 Q * pmenier Ping timeout: 480 seconds
1220806604 M * pmjdebruijn vargadani: that's too nasty to even speak of
1220806617 M * pmjdebruijn vargadani: compile your own kernel (2.6.22.19-vs2.2.0.7)
1220806636 M * vargadani yeah... that is what i did
1220806662 M * vargadani but the only thing I can right now think of is that for some reason my kernel just doesn't work
1220806666 M * vargadani as it is expected....
1220806679 M * vargadani or maybe I do something seriously wrong
1220806780 M * vargadani it will be enough for today.. will go on tomorrow
1220806857 Q * derjohn_mob Ping timeout: 480 seconds
1220807412 J * pmenier ~pmenier@ACaen-152-1-76-245.w83-115.abo.wanadoo.fr
1220807726 J * yarihm ~yarihm@85-62-239-77-pool.cable.fcom.ch
1220808127 Q * pmenier Quit: Konversation terminated!
1220808273 J * pmenier ~pmenier@ACaen-152-1-76-245.w83-115.abo.wanadoo.fr
1220808556 N * pmenier pmenier_off
1220809991 Q * doener Remote host closed the connection
1220810587 N * Bertl_oO Bertl
1220810593 M * Bertl back now ...
1220810672 Q * esa Ping timeout: 480 seconds
1220811729 J * doener ~doener@i577BA644.versanet.de
1220812332 M * vargadani ahm... i had a question a while ago about 127.0.0.1 and how it is handled... is it normal that in the guest I cannot see a lo interface and pinging 127.0.0.1 does nothing?
1220812356 M * Bertl depends on your kernel version and guest setup
1220812362 M * vargadani i suppose if I can't ping it, daemons cannot bind themselves to that interface either
1220812373 M * daniel_hozac ping has absolutely nothing to do with bind.
1220812376 M * vargadani 2.6.22.19-vs2.2.0.7
1220812388 M * Bertl daemons do not bind to interfaces, and ping is below the ip layer
1220812417 M * vargadani alright...
1220812427 M * Bertl vargadani: try 'ping localhost'
1220812437 M * Bertl if you setup is correct, that should work
1220812442 M * vargadani which works perfect
1220812475 M * vargadani so if I let's say have amavisd that binds itself to 127.0.0.1 should work, right?
1220812683 M * Bertl to _localhost_ yes
1220812705 M * vargadani yeah...well they have that silly IP address in the config file...
1220812711 M * Bertl binding to 127.0.0.1 is a bug in the daemon, but works fine for binding
1220812715 M * vargadani I think that messes things up a bit
1220812732 M * Bertl it might not work for access/security checks hardcoded to 127.0.0.1
1220812748 M * Bertl (unless you use vs2.3.x)
1220812762 M * vargadani the fact is that I used to be able to install Zimbra in vserver with no trouble at all but now I can't
1220812769 M * vargadani I used the very same vserver version
1220812781 M * vargadani so the only difference must be in zimbra...
1220812827 M * Bertl you can try with a vs2.3.x version, that gives the guest apps a perfect illusion of 127.0.0.1
1220812911 M * vargadani it is not stable yet, so I don't risk unless you say, that it is perfectly safe
1220812924 M * vargadani or at least as safe as the stable
1220812989 M * Bertl hehe, no, it's not as well tested .. but that was just a suggestion to test this theory with Zimbra
1220813003 M * Bertl i.e. to find out _if_ it is 127.0.0.1 related
1220813125 M * vargadani yeah... that makes sense
1220813146 M * vargadani if I weren't that lazy I would recompile my kernel right now :)
1220813188 Q * pisco_ Ping timeout: 480 seconds
1220813866 J * pisco ~pisco@tor.noreply.org
1220815631 Q * ktwilight Quit: dead
1220815727 Q * yarihm Quit: Leaving
1220815988 J * ktwilight ~ktwilight@118.208-66-87.adsl-static.isp.belgacom.be
1220816216 M * vargadani it is confirmed now that it not the system's fault that I cannot install zimbra properly... nor is it zimbra's fault...
1220816228 M * vargadani it's vmware that screws things up
1220816242 M * vargadani i am relieved
1220816476 J * ntrs ~ntrs@77.29.195.8
1220816518 Q * vargadani Remote host closed the connection
1220818052 J * vargadani ~vargadani@catv-89-135-16-217.catv.broadband.hu
1220818584 Q * NaioN Ping timeout: 480 seconds
1220819076 J * NaioN ~stefan@misc.mordor.unilogicnetworks.net
1220819640 J * ktwilight_ ~ktwilight@27.95-66-87.adsl-dyn.isp.belgacom.be
1220819745 Q * bonbons Quit: Leaving
1220819862 Q * ktwilight Ping timeout: 480 seconds
1220820769 Q * blues charon.oftc.net kinetic.oftc.net
1220820769 Q * mcp charon.oftc.net kinetic.oftc.net
1220820769 Q * cehteh charon.oftc.net kinetic.oftc.net
1220820769 Q * duckx charon.oftc.net kinetic.oftc.net
1220820769 Q * quote charon.oftc.net kinetic.oftc.net
1220820769 Q * padde charon.oftc.net kinetic.oftc.net
1220820769 Q * mEDI_S charon.oftc.net kinetic.oftc.net
1220820769 Q * morrigan charon.oftc.net kinetic.oftc.net
1220820769 Q * C14r charon.oftc.net kinetic.oftc.net
1220820769 Q * snooze charon.oftc.net kinetic.oftc.net
1220820769 Q * DoberMann charon.oftc.net kinetic.oftc.net
1220820769 Q * Bertl charon.oftc.net kinetic.oftc.net
1220820769 Q * eyck charon.oftc.net kinetic.oftc.net
1220820769 Q * bXi charon.oftc.net kinetic.oftc.net
1220820769 Q * fosco_ charon.oftc.net kinetic.oftc.net
1220820769 Q * SpComb charon.oftc.net kinetic.oftc.net
1220820769 Q * franck34 charon.oftc.net kinetic.oftc.net
1220820769 Q * cohan charon.oftc.net kinetic.oftc.net
1220820769 Q * pmjdebruijn charon.oftc.net kinetic.oftc.net
1220820769 Q * Adrinael charon.oftc.net kinetic.oftc.net
1220820769 Q * zbyniu charon.oftc.net kinetic.oftc.net
1220820769 Q * weasel charon.oftc.net kinetic.oftc.net
1220820769 Q * m_o_d charon.oftc.net kinetic.oftc.net
1220820769 J * C14r ~C14r@h58173.serverkompetenz.net
1220820769 J * bXi bluepunk@irssi.co.uk
1220820769 J * zbyniu ~zbyniu@host13-188.crowley.pl
1220820769 J * morrigan morrigan@IRC.13thfloor.at
1220820769 J * SpComb terom@zapotek.paivola.fi
1220820770 J * blues blues@ada117.neoplus.adsl.tpnet.pl
1220820771 J * franck34 franck34@sd-10138.dedibox.fr
1220820771 J * Adrinael adrinael@rid7.kyla.fi
1220820771 J * fosco fosco@212.85.148.86
1220820771 J * pmjdebruijn pascal@jester.pcode.nl
1220820771 J * weasel_ weasel@weasel.chair.oftc.net
1220820771 J * eyck 2aiolpjl@nat03.nowanet.pl
1220820771 J * snooze ~o@1-1-4-40a.gkp.gbg.bostream.se
1220820771 J * padde ~padde@patrick-nagel.net
1220820773 J * cohan ~cohan@koniczek.de
1220820777 J * duckx ~Duck@81.57.39.234
1220820779 N * weasel_ weasel
1220820779 J * m_o_d ~m_o_d@host-80.54.30.252.ltv.pl
1220820780 J * DoberMann ~james@cap31-6-88-180-72-76.fbx.proxad.net
1220820784 J * cehteh ~ct@pipapo.org
1220820813 J * mcp ~mcp@wolk-project.de
1220820828 J * mEDI_S ~medi@snipah.com
1220820900 J * androsch ~androsch@dslb-084-060-229-064.pools.arcor-ip.net
1220820945 N * DoberMann DoberMann[ZZZzzz]
1220821052 J * Bertl herbert@IRC.13thfloor.at
1220821069 J * Bertl_ herbert@IRC.13thfloor.at
1220821200 Q * ktwilight_ Quit: dead
1220821228 Q * Bertl_ 
1220821424 Q * vargadani Remote host closed the connection
1220821924 Q * loddafnir Remote host closed the connection
1220822054 J * ktwilight ~ktwilight@27.95-66-87.adsl-dyn.isp.belgacom.be
1220822066 J * ViRUS ~mp@p579B5386.dip.t-dialin.net
1220822111 J * Walex ~Walex@82-69-39-138.dsl.in-addr.zen.co.uk
1220822267 J * derjohn_mob ~aj@p5B23F987.dip.t-dialin.net
1220823032 J * Aiken ~Aiken@ppp118-208-124-125.lns4.bne4.internode.on.net
1220823342 Q * ntrs Ping timeout: 480 seconds
1220824328 J * Mojo1978 ~Mojo1978@ip-88-152-60-134.hsi.ish.de
1220824435 J * Frechemaus ~Frechemau@f049233246.adsl.alicedsl.de
1220824870 J * doener_ ~doener@i577B947D.versanet.de
1220824974 Q * doener Ping timeout: 480 seconds
1220827651 Q * Walex Read error: Connection reset by peer
1220827807 Q * ViRUS Quit: If there is Artificial Intelligence, then there's bound to be some artificial stupidity. (Thomas Edison)
1220827984 Q * Frechemaus 
1220828054 J * orzel ~orzel@freehackers.org
1220828134 M * orzel hello. I've been using vserver for several years and it's workign fine. For some days, processes keep on crashing inside the vm.
1220828166 M * orzel i've traced down the problem to this : i've added a ulimit in /etc/profile to limit the memory for my users. It seems this limit apply to processes in vserver, i dont know why
1220828180 M * orzel have you ever had this pb ?
1220828214 M * Bertl well, it really depends on your setup and kernel version
1220828266 M * Bertl but yes, host side ulimits can affect guests (on older kernels, without user spaces)
1220828274 M * orzel i use gentoo and my own kernel compiled from sources found on vserver.org : 2.6.22.2-vs2.2.0.3
1220828310 M * orzel to restart i do "vserver host restart" and i guess some bash script is used somewhere and read /etc/profile
1220828334 M * orzel i could ask a 'ulimit -v unlimited' in it if i knew which one is it, do you know ?
1220828342 M * Bertl vserver host? host is your name for the guest?
1220828350 M * orzel was an example
1220828369 M * orzel 'myclient' if you prefer, or 'myguest'
1220828380 M * Bertl so you have limits for root on the host?
1220828430 M * Bertl ulimit -Ha and ulimit -Sa will show you the limits
1220828459 M * daniel_hozac just set explicit limits in /etc/vservers/<guest>/ulimits and they will be honored.
1220828462 Q * Mojo1978 Read error: Connection reset by peer
1220828556 M * orzel daniel_hozac:  what is the format of this file ?
1220828823 M * Bertl http://www.nongnu.org/util-vserver/doc/conf/configuration.html
1220828900 M * orzel ok the problem is now fixed, and the vserver processes are not limited, while those from people connecting through ssh are. which is great.
1220828903 M * orzel thanks for your help!
1220828913 M * Bertl you're welcome!
1220828952 M * orzel btw, i'm looking forward to two things : ipv6 support, and support for linux kernel 2.6.26 or 27
1220828966 M * Bertl it's already there :)
1220828980 M * orzel not on the main page 
1220828995 M * orzel i mean, of course, 'production ready' :)
1220829007 M * Bertl well, Experimental for now
1220829044 M * orzel your naming scheme is strange. vs2.2.0.3 can apply to  kernel 2.6.19.7 and 2.6.22.2 too ?
1220829051 M * cehteh hehe .. vserver is one of these projects, anyone uses in production but almost noone tests :)
1220829066 M * orzel cehteh: you frighten me!
1220829073 M * Bertl orzel: vs2.2.x means second stable branch
1220829084 M * Bertl orzel: that can apply to a number of kernels
1220829103 M * Bertl (similar for vs2.3.x which is the devel branch)
1220829104 M * cehteh orzel: i meant anyone has production server with it .. but if asked to test it .. "Huh .. no server for that" ;)
1220829109 M * cehteh at least happens to me
1220829131 M * orzel mm, how dangerous is the use of 2.3 ?
1220829144 M * Bertl not really
1220829163 M * cehteh iirc lot people use it for production
1220829194 M * orzel There's also, imha, a huge psychological point : your main page is reassuring, it looks great, while the 'experimental' stuff is a dir listing. I did ^W as soon as I've seen  that
1220829228 M * cehteh dir listings are pure information at the fingertips
1220829231 M * Bertl well, stable is well tested, that's the point
1220829242 M * cehteh do you want a marketing department for the experimental patches? :)
1220829248 M * orzel just do a great wiki  page as good-looking as the production version table stuff, so people know where to go / what to use/
1220829258 M * orzel cehteh: a wiki page will be enough :)
1220829267 M * cehteh its a wiki .. make one 
1220829274 M * Bertl orzel: feel free to create wiki pages around my upload dir
1220829307 M * orzel i dont know what to put in it... that's precisely what i would find such a page useful
1220829312 M * orzel for
1220829349 M * Bertl well, if you do not know what to write on such a page, what do you expect from that page?
1220829371 M * orzel i would expect the information i'm looking for : what to use/test
1220829379 M * orzel i dont know this, so i can't write the page, can I?
1220829436 M * Bertl ah, well, it's quite simple: if you want stable, use the stable branch, if you want new features, use the development branch, if you want bleeding edge stuff, go for Experimental
1220829456 M * orzel argh. there are three branches ? see.. i thought there was two
1220829462 M * orzel were
1220829477 M * Bertl of course, if you want to do testing, then Experimental is where you should be
1220829496 M * orzel 2.3 is 'deve branch' ?
1220829524 M * Bertl yes, and vs2.3.x are devel releases
1220829541 M * orzel ok, and which ones are experimental ?
1220829558 M * Bertl note that the experimental branch has no separate numbering, it just has another extension
1220829568 M * orzel ah, ok
1220829570 M * Bertl i.e. vs2.3.0.35 is experimental (strictly speaking)
1220829576 M * orzel ok, i understand
1220829590 M * Bertl but that is actually quite stable and we will probably promote it soon
1220829598 M * Bertl (to development)
1220829601 Q * balbir_ Ping timeout: 480 seconds
1220829618 M * orzel so there's no 'dev' for 2.6.26/27 kernel and/or  ipv6 yet. But only experimental ones
1220829627 M * Bertl which will eventually become the next stable (vs2.4)
1220829637 M * orzel i understand the flow :)
1220829645 M * Bertl for ipv6 there are devel branches for older kernels
1220829655 M * orzel ok
1220829668 M * Bertl for 2.6.26 (which is quite experimental too :) there are only experimental releases for now
1220829712 Q * SlackLnx Quit: I'll Be back
1220829770 M * orzel ok. So my best bet would be to use patch-2.6.26.3-vs2.3.0.35.5.diff  , knowing that it's almost considered stable enough to be promoted to 'dev' soon.
1220829797 M * Bertl yep, that gives you 2.6.26 and ipv6
1220829808 M * Bertl (and a bunch of other new features)
1220829823 M * orzel ok, i might do just that :)
1220830180 J * zbyniu_ ~zbyniu@host13-188.crowley.pl
1220830190 Q * zbyniu Read error: Connection reset by peer