1223424416 M * Bertl okay, off to bed now .. have a good one everyone!
1223424425 N * Bertl Bertl_zZ
1223424525 Q * BrunoXLambert Quit: Leaving
1223425213 J * ghislainocfs21 ~Ghislain@adsl2.aqueos.com
1223425609 Q * ghislainocfs2 Ping timeout: 480 seconds
1223426754 J * ghislainocfs2 ~Ghislain@adsl2.aqueos.com
1223427077 Q * ghislainocfs21 Ping timeout: 480 seconds
1223427432 M * Bertl_zZ df
1223428886 J * doener_ ~doener@i577BB9D5.versanet.de
1223428987 Q * doener Ping timeout: 480 seconds
1223434445 Q * doener_ Quit: leaving
1223435697 Q * mattzerah Ping timeout: 480 seconds
1223436028 J * ghislainocfs21 ~Ghislain@adsl2.aqueos.com
1223436356 Q * ghislainocfs2 Ping timeout: 480 seconds
1223436512 J * ghislainocfs2 ~Ghislain@adsl2.aqueos.com
1223436530 J * ktwilight_ ~ktwilight@80.76-66-87.adsl-dyn.isp.belgacom.be
1223436782 Q * ghislainocfs21 Ping timeout: 480 seconds
1223436814 Q * ktwilight Ping timeout: 480 seconds
1223437674 J * ghislainocfs21 ~Ghislain@adsl2.aqueos.com
1223437923 Q * ghislainocfs2 Ping timeout: 480 seconds
1223438183 J * mattzerah ~matt@pool1-180.dyn.winshop.com.au
1223438531 Q * mattzerah Read error: Operation timed out
1223441519 J * FireEgl Proteus@2001:470:e056:1:4::
1223442602 J * mattzerah ~matt@pool1-180.dyn.winshop.com.au
1223443065 J * ntrs__ ~ntrs@77.29.66.197
1223443264 J * kir ~kir@swsoft-msk-nat.sw.ru
1223443342 J * sharkjaw ~gab@149-67-194.231210.adsl.tele2.no
1223443493 N * Bertl_zZ Bertl_oO
1223443503 M * Bertl_oO off to the airport ... hopefully bbl
1223443579 M * Supaplex take care :)
1223446175 J * mtg ~mtg@vollkornmail.dbk-nb.de
1223446786 Q * hparker Quit: Read error: 104 (Peer reset by connection)
1223447208 J * ntrs_ ~ntrs@77.29.74.74
1223447518 J * ntrs ~ntrs@77.29.75.94
1223447652 Q * ntrs__ Ping timeout: 480 seconds
1223447843 Q * ntrs_ Ping timeout: 480 seconds
1223448194 Q * larsivi Quit: Konversation terminated!
1223448603 Q * mtg Quit: Verlassend
1223449489 Q * ghislainocfs21 Quit: Leaving.
1223449505 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr
1223449656 Q * infowolfe Ping timeout: 480 seconds
1223450509 J * mtg ~mtg@dialbs-088-079-143-204.static.arcor-ip.net
1223451312 Q * ntrs Ping timeout: 480 seconds
1223451588 Q * mtg Quit: Verlassend
1223451907 J * larsivi ~larsivi@85.221.53.194
1223453892 J * mtg ~mtg@vollkornmail.dbk-nb.de
1223454460 J * moemoe moemoe@kuschelhoelle.netzhure.de
1223454928 J * quinq ~quinq@quinq.eu.org
1223456228 J * mtgx ~mtg@vollkornmail.dbk-nb.de
1223456644 J * Punkie ~Punkie@goc.coolhousing.net
1223456997 Q * larsivi Ping timeout: 480 seconds
1223457760 J * larsivi ~larsivi@85.221.53.194
1223458298 J * yarihm ~yarihm@hg-public-dock-76-dhcp.ethz.ch
1223461228 Q * nkukard Quit: Leaving
1223462228 Q * yarihm Ping timeout: 480 seconds
1223463875 J * yarihm ~yarihm@hg-public-dock-155-dhcp.ethz.ch
1223465112 Q * yarihm Ping timeout: 480 seconds
1223465654 M * larsivi hi - I'm having trouble with accessing a vserver via ssh after a restart, and when I enter it, I'm not getting out from it either
1223465665 M * larsivi I'm able to ssh to it from the host itself though
1223465685 M * larsivi where did I mess up this time? ._.
1223465821 Q * moemoe Quit: leaving
1223466070 M * PowerKe What do you mean by 'not getting out from it'? Not being able to make outgoing network connections?
1223466732 M * larsivi PowerKe: yeah - outoing and ingoing - except to/from stuff on same switch
1223466768 M * PowerKe Are you using a different subnet on host and guests?
1223466912 Q * quinq Quit: Quitte
1223466950 J * quinq ~IRC@quinq.eu.org
1223467287 M * larsivi PowerKe: shouldn't be
1223467320 M * larsivi PowerKe: the restart was due to a power shortage, it worked perfectly fine prior to that
1223467340 M * larsivi hmm, I have an idea ..
1223467654 Q * quinq Remote host closed the connection
1223467690 J * quinq ~IRC@quinq.eu.org
1223467707 J * larsivi_ ~larsivi@85.221.53.194
1223467847 M * larsivi_ PowerKe: was able to solve it, a different box had nicked the ip address
1223467912 Q * larsivi Ping timeout: 480 seconds
1223470112 Q * Aiken Remote host closed the connection
1223471047 J * dna ~dna@42-197-dsl.kielnet.net
1223471413 J * docelic ~docelic@78.134.200.56
1223471598 Q * sharkjaw Remote host closed the connection
1223472253 J * glen_ ~glen@elves.delfi.ee
1223472268 M * glen_ in scripts/pre-start, post-stop, what evn variables are available?
1223472280 M * glen_ i mean i would like to know what is my vserver config dir the scrips are run
1223472341 M * glen_ only thing i see which came from util-vserver is this var:
1223472342 M * glen_ -INIT_CWD=/vservers/wintersunset
1223472342 M * glen_ +INIT_CWD=/
1223472466 N * ensc Guest118
1223472466 Q * Guest118 Remote host closed the connection
1223472476 J * ensc ~irc-ensc@77.235.182.26
1223473647 J * lilalinux ~plasma@80.69.41.3
1223474382 Q * larsivi_ Ping timeout: 480 seconds
1223475764 J * psycotux ~psycotuxb@snappy.schneebi.com
1223475808 Q * kir Quit: Leaving.
1223475815 M * psycotux hello, I am on debian etch and i need temporarily for a setup 127.0.0.1 in a vserver guest, is there any way i can achieve this ?
1223475918 Q * mtgx Quit: Verlassend
1223475918 Q * mtg Quit: Verlassend
1223476073 M * pmjdebruijn psycotux: for which application?
1223476080 M * pmjdebruijn psycotux: most apps can also use the external ip
1223476111 M * psycotux pmjdebruijn, for ssl-explorer enterprise, a java application that insists on running the setup wizard on localhost.
1223476139 M * mnemoc psycotux: vserver 2.3 supports per-context localhosts
1223476167 M * mnemoc psycotux: and if it uses the "name" localhost, you can tweak it in /etc/hosts
1223476181 M * pmjdebruijn indeed
1223476191 M * pmjdebruijn psycotux: to what does it connect? 127.0.0.1? or localhost?
1223476192 M * psycotux mnemoc, i've seen that, but i guess i am on an earlier version, i couldn't figure how to find out what my vserver version is, it ist what is shipped with debian 4.0
1223476210 M * pmjdebruijn psycotux: that's an old version anyway
1223476219 M * pmjdebruijn most folks build their own kernels
1223476226 M * psycotux mnemoc, thx ill try about the localhost trick, but i guess it will connect to 127.0.0.1 directly, it wants to run on that for security reasons
1223476286 M * psycotux pmjdebruijn, i prefer to use the shipped kernels within debian, i highly enjoy that they come with vserver support built in
1223476301 M * pmjdebruijn psycotux: it's a VPN app
1223476309 M * pmjdebruijn seems like the kind of app, you don't want to virtualize anwyays
1223476314 Q * Punkie Quit: ...mizim...
1223476325 M * pmjdebruijn psycotux: I've never really taken the debian vanilla kernels seriously
1223476333 M * pmjdebruijn but I get your point
1223476370 M * psycotux pmjdebruijn, it works beautifully, i migrated it from vmware where i set it up originally - worked like a charm for months, but now i have upgraded it for reasons and it won't start anymore since it wants to run the wizard for me to check the settings *arghlsfx*
1223476436 M * psycotux so if i get you right, in my version theres no ugly hack that allows my i.e. to expose the hosts lo to the guest for a minute or two ?
1223476448 M * pmjdebruijn not that I know of...
1223476452 M * pmjdebruijn but I never really tried
1223476581 M * psycotux so i have no choice than bringing it back to vmware, upgrading it, and migrating it back to vserver, ha IT-jobs are fun at times ;) I'll probably restore backup and bug the vendor about it... thanks for the hints anyway!
1223476755 M * ktwilight_ why not just upgrade vserver? would be easier...and less hassle in the long run
1223476760 M * pmjdebruijn true
1223476762 M * pmjdebruijn but it's still beta
1223476790 M * ktwilight_ what is?
1223476860 M * ktwilight_ you mean 2.3.x?
1223476875 M * psycotux tempting, tempting, but i am happy with the current version despite the 127.0.0.1 probs which are very rare (i run ~25 guests and all fine). And staying with what debian gives you is sometimes a bit boring and a wait, but it has proved to be a good choice regarding stability
1223476996 M * ktwilight_ i guess so far whatever that's on vserver's site is good for me. though i have yet to try out 2.3.x, but i haven't hear anything bad so far
1223477006 M * ktwilight_ s/that's/what's
1223477794 M * psycotux how can i find out what version of vserver patch is applied to a kernel ? 
1223477867 M * ktwilight_ main site has it linux-vserver.org
1223478394 M * psycotux ktwilight_, hmm - with 2.16.18 i guess i run 2.2, also since all 2.3 are beta ias pmjdebruijn mentioned it seems not worth checking lenny, i am almost sure they have 2.2 too
1223479139 J * doener ~doener@i577BB9D5.versanet.de
1223479259 Q * docelic Quit: http://www.spinlocksolutions.com/
1223479744 J * lilalinux_ ~plasma@dslb-084-058-251-254.pools.arcor-ip.net
1223480012 A * ard has checked that
1223480019 M * ard the 2.6.26 kernel of lenny contains 2.3
1223480061 M * ard etch has 2.0 I guess
1223480176 Q * lilalinux Ping timeout: 480 seconds
1223480778 J * mtg ~mtg@dialbs-088-079-143-204.static.arcor-ip.net
1223481614 M * mnemoc psycotux: 2.3 aint "beta"
1223481665 M * mnemoc psycotux: it's stable but not feature frozen or as mature as 2.2
1223481768 M * psycotux ard, ty, thats really cool and saves my elsewise spoilt day completely ;)
1223481773 Q * lilalinux_ Remote host closed the connection
1223481818 M * pmjdebruijn mnemoc: is that true?
1223481834 M * ktwilight_ it's true
1223481848 M * ktwilight_ daniel_hozac and Bertl_oO mentioned the same
1223481855 M * ktwilight_ though, then again, both of 'em are core devs of vserver
1223481866 J * hparker ~hparker@linux.homershut.net
1223481894 M * mnemoc pmjdebruijn: as far as you don't try the lastest patch against the lastest -rc of the kernel, it _is_ stable
1223481902 M * pmjdebruijn ok
1223481914 M * pmjdebruijn so 2.6.26 should be stable
1223481921 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d
1223481929 M * psycotux how come there is no method to identify what version of the patch is running in a kernel ?
1223481944 J * dowdle ~dowdle@scott.coe.montana.edu
1223482053 M * mnemoc pmjdebruijn: http://vserver.13thfloor.at/Experimental/ ... if it doesn't say -pre, it's stable =)
1223482110 M * mnemoc pmjdebruijn: http://vserver.13thfloor.at/Experimental/patch-2.6.26.5-vs2.3.0.35.6.diff should be pretty solid
1223482116 M * pmjdebruijn ok, right
1223482195 M * mnemoc psycotux: cat /proc/virtual/info 
1223482214 M * pmjdebruijn psycotux: etch's patch is ancient
1223482239 M * pmjdebruijn ls
1223482241 M * pmjdebruijn sorry
1223482375 M * psycotux mnemoc, ty, how do i interpret those 3 lines ? (sorry if this sounds dumb, but I only get "VCIVersion:     0002:0002\nVCISyscall:     236\nVCIKernel:      03000076")
1223482393 M * mnemoc as ancient :)
1223482401 M * psycotux *lol* 
1223482421 M * psycotux ok, so you say in a non-ancient version this would be meaningful in some way ?
1223482421 M * mnemoc 2.0
1223482438 M * pmjdebruijn btw, is anybody here already running customers on 2.6.26.5-vs2.3.0.35.6 ?
1223482488 M * mnemoc pmjdebruijn: when you have customers running, you should consider to have a test server =)
1223482497 M * pmjdebruijn mnemoc: obviously
1223482531 M * pmjdebruijn mnemoc: but I've found it's hard to really reproduce a production environment with a test setup
1223482788 J * rooijan ~rrosso@cuba.sonosite.com
1223484621 Q * mtg Quit: Verlassend
1223486697 Q * _gh_ Ping timeout: 480 seconds
1223487289 J * ntrs ~ntrs@77.29.65.175
1223487444 J * nkukard ~nkukard@196.212.73.74
1223487700 Q * micah Read error: Connection reset by peer
1223487767 J * micah ~micah@micah.riseup.net
1223488518 J * cga ~weechat@94.36.108.221
1223489005 J * _gh_ ~gerrit@129.33.192.59
1223490718 J * ntrs_ ~ntrs@77.29.65.230
1223490751 J * yarihm ~yarihm@77-56-182-18.dclient.hispeed.ch
1223491127 Q * ntrs Ping timeout: 480 seconds
1223492739 J * chigital ~chigital@tmo-117-26.customers.d1-online.com
1223496825 J * xdr ~xdr@62-173-96-87.cust.blixtvik.se
1223497403 J * Psy0rz ~psy0rz@lounge.datux.nl
1223497421 M * Psy0rz is it posible to have a real 127.0.0.1 or lo adapter inside a guest?
1223497440 M * Psy0rz instead of the ugly hack there http://linux-vserver.org/Problematic_Programs#127.0.0.1_issues
1223497445 M * daniel_hozac set CONFIG_VSERVER_AUTO_LBACK when configuring your kernel.
1223497457 M * daniel_hozac (assuming it is Linux-VServer 2.3 based)
1223497476 M * Psy0rz i have 2.2.0.7
1223497485 M * Psy0rz i'm fucked? ;)
1223497533 M * daniel_hozac yes.
1223497541 M * Psy0rz k
1223497551 M * Psy0rz then i'll just hack around for now and wait until 2.3 gets stable :)
1223497552 M * Psy0rz thx
1223497673 Q * bonbons Quit: Leaving
1223498659 J * docelic ~docelic@78.134.200.56
1223499266 Q * cga Quit: WeeChat 0.2.6
1223499522 J * Aiken ~Aiken@ppp118-208-28-181.lns2.bne1.internode.on.net
1223503109 J * infowolfe ~infowolfe@c-67-160-149-42.hsd1.or.comcast.net
1223503234 J * derjohn_mob ~aj@p5B23DC34.dip.t-dialin.net
1223503336 Q * ntrs_ Ping timeout: 480 seconds
1223503493 Q * hparker Quit: Quit
1223504468 Q * docelic Quit: http://www.spinlocksolutions.com/
1223504697 Q * chigital Ping timeout: 480 seconds
1223506285 Q * yarihm Quit: Leaving
1223508308 J * hparker ~hparker@linux.homershut.net
1223509774 Q * quinq Remote host closed the connection
1223509811 J * quassel251 ~quassel@quinq.eu.org
1223509897 Q * quassel251 
1223509931 J * quinq ~user@quinq.eu.org
1223510104 Q * quinq Remote host closed the connection