1166659504 Q * click Ping timeout: 480 seconds 1166660514 P * stefani I'm Parting (the water) 1166660663 Q * newz2000 Ping timeout: 480 seconds 1166661222 Q * dna Quit: Verlassend 1166661972 Q * ruskie Remote host closed the connection 1166662995 J * newz2000 ~matt@12-207-9-218.client.mchsi.com 1166664579 M * bronson neuralis: source package fixed. 1166664601 M * bronson Sorry for the delay -- I was taken real low by a cold. 1166664620 N * Bertl_zZ Bertl 1166664626 M * bronson wb Bertl 1166664631 M * Bertl morning folks! 1166664659 M * bronson Had a chance to look at 2.6.20? :) 1166664661 M * bronson Just curious. 1166664683 M * daniel_hozac what's so special about 2.6.20? 1166664685 M * daniel_hozac morning Bertl! 1166664685 M * Bertl yeah, I had a look, but didn't start porting yet 1166664694 M * Kerberos kvm on 2.6.20 1166664706 M * Bertl not much has changed, I expected the entire pid stuff to get in 1166664711 M * daniel_hozac yeah, me too. 1166664712 M * Bertl (well, maybe it will :) 1166664717 M * daniel_hozac seems it's just prepared for that now. 1166664966 M * bronson I'd like to try to prepare a Feisty (2.6.20) kernel now that Edgy seems to be finished and working... Is vs2.3.0.4 the patch to start from? 1166665035 M * daniel_hozac you realize it's just at 2.6.20-rc_1_, right? 1166665057 M * bronson daniel_hozac: of course. 1166665065 M * bronson Sorry for taking a shortcut. :) 1166665179 M * daniel_hozac so then you're aware there'll be something like another MiB of bzip2'd changes before 2.6.20 is final? 1166665213 M * bronson Sure. I'd just like to see how painful it is. 1166665276 M * bronson So... it sounds like vs2.3.0.4 is the best patch to start with...? 1166665312 M * bronson I'm just asking if anyone is playing with anything later so I don't end up duping somebody else's work. 1166665313 M * Bertl a good choice, but probably 2.2.0-rc* would be more interesting 1166665352 M * bronson 2.2.0-rc5? OK, will do. 1166665354 M * bronson Bertl: thakns. 1166665357 M * bronson thanks. 1166665603 J * FireEgl ~FireEgl@adsl-61-147-76.bhm.bellsouth.net 1166667019 J * MrX ~chaos@218.208.211.250 1166667069 J * ntrs ~ntrs@68-188-55-120.dhcp.stls.mo.charter.com 1166667611 Q * newz2000 Quit: We are leaving! - quote from Doom with Aliens wad 1166669192 J * ruskie ~ruskie@ruskie.user.oftc.net 1166669754 Q * tamitall Quit: Leaving 1166670214 Q * id23 Ping timeout: 480 seconds 1166670738 J * id23 ~id@p50812159.dip0.t-ipconnect.de 1166670890 Q * hardwire Quit: Coyote finally caught me 1166671513 M * ntrs Hi, I think the v_httpd script does not work properly. 1166671521 M * ntrs httpd is started but is not listening on any port 1166671550 M * ntrs # /etc/init.d/v_httpd restart 1166671550 M * ntrs exec /usr/sbin/chbind --ip eth0 /etc/init.d/httpd restart 1166671550 M * ntrs New network context is 49156 1166671550 M * ntrs Adding 87.xxx.xxx.xxx 1166671550 M * ntrs Stopping httpd: [ OK ] 1166671551 M * ntrs Starting httpd: [ OK ] 1166671645 M * ntrs Bertl, do you have any ideas about this problem? 1166671809 Q * lilalinux Remote host closed the connection 1166672076 M * ntrs Bertl, this is the weirdest thing. 1166672091 M * ntrs The httpd processes are there and are serving pages normally 1166672108 M * ntrs I can see the processes with ps aux but netstat -anlp does not show the bindingd. 1166672111 M * ntrs nidings 1166672119 M * ntrs bindings. 1166672142 Q * DreamerC_ Quit: leaving 1166672159 J * DreamerC ~dreamerc@125-225-96-17.dynamic.hinet.net 1166673131 M * Bertl hmm 1166673145 M * phreak`` yeah ? :) 1166673149 M * Bertl ntrs: ah, 2.2 or 2.3 ? 1166673170 M * ntrs 2.2.0-rc5 1166673176 M * Bertl then that is fine 1166673181 M * ntrs fine? how? 1166673187 M * ntrs I don't think it's fine 1166673192 M * Bertl the bindings will be shown in the network context you used 1166673208 M * ntrs previously it was always the server context 1166673212 M * Bertl in this case, you have to enter the 49156 (or whatever context it is) 1166673222 M * Bertl yep, that is something which was fixed 1166673231 M * ntrs It is unnatural to start a service with v_httpd and not see that in the host context. 1166673256 M * Bertl well, the v_* wrappers should have gone away some time ago 1166673269 M * ntrs after you start it and login again after 20 days how do you remember which context it was started under? 1166673287 M * Bertl soon the dynamic contexts will be disabled too 1166673305 M * ntrs If they went away, how can I start a httpd process in the host context? 1166673305 M * Bertl at this point, userspace will probably use a specific context for that 1166673329 M * Bertl e.g. 65535 for v_* functionality 1166673344 M * Bertl or 666 if you prefer :) 1166673346 M * ntrs ok, but what can I do now? 1166673362 M * Bertl first, you can forget about the dynamic ids 1166673367 M * ntrs I want to start the process and be able to see it in the host context./ 1166673379 M * ntrs I never use dynamic ids. 1166673382 M * Bertl i.e. use a static right now, then you can see it _in_ that context 1166673393 M * Bertl well, 49156 _is_ a dynamic id 1166673415 M * ntrs that is used by the v_httpd script I guess. I never personally set anything to use dynamic ids 1166673422 M * Bertl but as I said, I think this is something which needs fixing 1166673426 M * ntrs how can I instruct it to use xid 1? 1166673438 M * Bertl i.e. the v_* wrappers have to be adjusted 1166673446 M * Bertl (or removed) 1166673478 M * Bertl basically you can get the same (but controlled) functionality if you add a 1166673511 M * Bertl chbind --nid 666 --ip -- 1166673542 M * Bertl that will, as usual, throw the program into a neetwork context, and allow binding to the host ip only 1166673583 M * ntrs ok, can I use nid 1? 1166673591 M * ntrs to set it in the host context? 1166673608 M * Bertl better not, because that will get the spectator funtionality 1166673620 M * Bertl I think it is already blocked 1166673671 M * ntrs It was so nice to be able to see it in the host before. I don't like the new functionality. 1166673696 M * Bertl well, the problem is, the old functionality was clearly a bug 1166673719 M * Bertl you basically saw a socket on the host 1166673745 M * Bertl which wasn't allowed to bind to all ips, but with the typical IP_ADDR_ANY binding 1166673770 M * Bertl instead, the process was (and is now too, that didn't change) inside a network namespace 1166673808 M * Bertl so, instead of showing bindings which are not true, we changed it to show the actual _host_ bindings only 1166673832 M * Bertl i.e. those which are not inside a network namespace 1166673897 M * ntrs ok, I understand that, but I still think it was more convenient the other way. 1166673938 M * ntrs I think you'll see more complaints about this as more people adopt using 2.2.0-rcX and later. 1166674001 M * Bertl well, while this might be, I don't think that misleading information is something we should enforce ... that aside, the new network requirements are not able to emulate this misbehaviour anymore 1166674026 M * Bertl I assume we will get most complaints because many folks are still using dynamic contexts 1166674051 M * Bertl but we are warning about that for two? years now, so I think it is time to adjust 1166674055 M * ntrs No, I use exclusively static contexts. 1166674066 M * ntrs I see what you mean. 1166674079 M * ntrs Someone will have to adjust. :) 1166674111 M * Bertl but yes, the v_* wrappers are basically broken 1166674127 M * Bertl will talk to daniel_hozac regarding possible solutions 1166674246 M * ntrs ok 1166674399 M * ntrs I tried to check on the process with netstat -anlp with this: 1166674400 M * ntrs # chcontext --xid 49158 netstat -anlp 1166674400 M * ntrs vcontext: vc_ctx_migrate(): No such process 1166674409 M * ntrs chcontext seems to be broken too. 1166674787 M * Bertl nope, wrong tool 1166674799 M * Bertl use vncontext 1166674808 M * Bertl it is a network context, not a process context 1166674859 M * Bertl sec, not sure it is called vncontext in util-vserver 1166675092 M * Bertl it's called ncontext 1166675120 M * Bertl ncontext --migrate --nid 49158 -- netstat -anlp 1166676225 J * Aiken_ ~james@tooax8-191.dialup.optusnet.com.au 1166676553 Q * Aiken Ping timeout: 480 seconds 1166676675 J * hardwire ~hardwire@rdbck-4891.wasilla.mtaonline.net 1166678952 Q * bronson Quit: Ex-Chat 1166678955 J * bronson ~bronson@adsl-75-36-149-233.dsl.pltn13.sbcglobal.net 1166683068 Q * Aiken_ Quit: Leaving 1166683229 J * Aiken ~james@tooax8-191.dialup.optusnet.com.au 1166685363 Q * kir Ping timeout: 480 seconds 1166686531 J * Fire_Egl ~FireEgl@adsl-61-147-76.bhm.bellsouth.net 1166686690 Q * FireEgl Read error: Operation timed out 1166686842 M * svendag hi .. i've a strange problem .. my system is a debian amd64 sarge which 6 vhosts based on debian .. all is working perfectly .. but i've problems, to get a gentoo system working .. any time i want to start the vserver i get the following error message: 1166686854 M * svendag master:~# vserver ws01 start 1166686855 M * svendag No command given; use '--help' for more information. 1166686855 M * svendag An error occured while executing the vserver startup sequence; when 1166686855 M * svendag there are no other messages, it is very likely that the init-script 1166686855 M * svendag () failed. 1166686875 M * svendag any ideas where i can look for the reason? :) 1166687331 Q * MrX Quit: X 1166688958 M * Hollow svendag: which stage tarball and init-style do you use? 1166689221 Q * id23 Remote host closed the connection 1166690690 Q * Aiken Read error: Connection reset by peer 1166692618 J * dna ~naucki@141-232-dsl.kielnet.net 1166692695 M * svendag i've used stage 3 stabel and experimental .. the initial setup was done in an chroot enviroment .. then i thought, ok .. fine .. creted the /etc/vservers/hostname dir and configured the files for the vserver .. 1166692718 J * kir ~kir@swsoft-mipt-nat.sw.ru 1166692809 M * svendag i'm using sysvinit .. or what do you mean? :) 1166693364 M * Hollow svendag: i mean /etc/vservers/apps/init/style .. but for gentoo you either need vserver stages (and use baselayout-vserver), or you can download the experimental stage with baselayout-1.13 which should work out of the box, and unless you're using >=util-vserver-0.30.211 i suggest to use plain init style 1166693445 J * onion onion@virasto.com 1166693752 M * onion hi all! I'm using vserver on dhcp-enabled server. My server's (eth0, eth1) ip address tend to change at sometimes. Is it possible to configure vserver to use interface without configuring ip and mask, nodev style? (vs2.0.3, util-vserver 0.30.204) 1166694089 J * _dmax ~semaj@bl4-61-243.dsl.telepac.pt 1166694108 J * s0undt3ch_ ~s0undt3ch@81.193.61.243 1166694161 Q * s0undt3ch Killed (NickServ (GHOST command used by s0undt3ch_)) 1166694161 N * s0undt3ch_ s0undt3ch 1166694211 Q * dmax Ping timeout: 480 seconds 1166694215 N * _dmax dmax 1166694517 J * pisco ~pisco@tor-irc.dnsbl.oftc.net 1166694845 M * matti Morning ;) 1166694966 Q * dna Quit: Verlassend 1166695425 M * Bertl onion: no, but you can assign a private ip to your guest 1166695445 M * Bertl onion: and then use S/DNAT to remap that to the 'current' one 1166695494 M * Bertl onion: it cannot work in any other way, because when the ip address changes, all existing connections would have to 'change' too 1166695580 M * onion Bertl: ok, thx... I'll just put up dhclient-exit-hook script to write out ip/mask to vserver config dir... 1166695615 M * Bertl hmm, okay, but that won't help with a dynamic change 1166695640 M * Bertl more than that, it will stop your guest from shutting down properly if the address is changed on the fly 1166695652 M * onion Bertl: yes, true. but haven't seen it happen... 1166695666 M * Bertl okay :) 1166695714 M * onion Bertl: dhcp3-client send's dhcprelease at server shutdown, then it loses it's original ip. 1166696086 Q * morfoh charon.oftc.net unununium.oftc.net 1166696086 Q * bon charon.oftc.net unununium.oftc.net 1166696086 Q * neuralis charon.oftc.net unununium.oftc.net 1166696088 J * bon bon@stichting-brein.eu 1166696090 M * onion quick fix, unplug server when shutting down (when using isc dhcp3 client) :) 1166696118 J * morfoh ~morfoh@kilo105.server4you.de 1166696123 M * matti Eh. 1166696148 J * neuralis ~krstic@solarsail.hcs.harvard.edu 1166696682 J * niol ~niol@sousmonlit.dyndns.org 1166696881 M * niol hi all, an Oops occurs everytime I stop a vserver (this is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402743 ), any ideas? 1166697153 J * Aiken ~james@tooax6-212.dialup.optusnet.com.au 1166697304 M * onion niol: is it debian's stock kernel? 1166697348 M * Bertl niol: a lot of information is missing, dmesg probably has more, but not sure you can capture it without serial console 1166697382 M * Bertl niol: nevertheless, I'd try a more recent kernel and/or a mainline (read kernel.org + Linux-VServer patch) kernel 1166697437 M * Bertl niol: if you encounter this issue with, let's say 2.6.19.1-vs2.2.0-rc5, we have something to fix :) but I doubt that it will happen 1166697731 Q * onion Quit: cya 1166697753 M * niol onion: it is debian stock kernel 1166697864 M * niol Bertl: there is an attachment in the bug report and the output from my machine is at http://sousmonlit.dyndns.org/~niol/tmp/vserver.stop.dmesg 1166697954 M * Bertl interesting, but should not happen 1166697984 M * Bertl is that reproduceable? 1166697994 M * Bertl i.e. do you get that on every shutdown? 1166698011 M * niol Bertl: yep 1166698052 M * Bertl in this case, please try with mainline, so that we can check if it is a Linux-VServer bug or a debian one 1166698188 M * niol okay, you mine the vanilla 2.6.18 with vserver patch? 1166698208 M * Bertl well, I'd suggest to go for 2.6.19.1 1166698218 M * Bertl but yes, the idea is kernel + patch 1166698258 M * Bertl http://vserver.13thfloor.at/Experimental/patch-2.6.19.1-vs2.2.0-rc5.diff 1166698317 M * niol okay so I'll do that later today and get back here 1166698334 M * Bertl excellent, TIA! 1166698375 M * niol Do you know where I can find a detailed changelog of the vserver patch to see if this has already been addressed? 1166698407 M * Bertl I can assure you, this issue was not addressed yet 1166698436 M * Bertl i.e. either mainline fails with the same one, or debian did introduce a bug somewhere 1166698482 M * niol okay thanks see you later (I connect from the machine that runs vserver, so I need to go to mess with the kernel...) 1166698507 M * Bertl okay, np, might be off to bed soon, but just leave me a message here 1166698517 M * niol sure 1166698519 M * niol see you 1166698523 Q * niol Quit: leaving 1166698908 J * Johnsie ~jdlewis@jdlewis.org 1166699298 J * daniel_hozac|irssi ~daniel@c-2c1472d5.010-230-73746f22.cust.bredbandsbolaget.se 1166699327 Q * Adrinael Remote host closed the connection 1166699329 J * Adrinael adrinael@st12-127.tky.hut.fi 1166699346 Q * Johnnie Ping timeout: 480 seconds 1166699347 Q * daniel_hozac Read error: No route to host 1166701265 Q * mire Ping timeout: 480 seconds 1166701813 J * mire ~mire@40-167-222-85.adsl.verat.net 1166702531 Q * ensc Killed (NickServ (GHOST command used by ensc_)) 1166702541 J * ensc ~irc-ensc@p54B4D87F.dip.t-dialin.net 1166703059 J * nou Chaton@causse.larzac.fr.eu.org 1166703175 M * Bertl okay, off to bed now ... have a good one everyone ... cya! 1166703182 N * Bertl Bertl_zZ 1166703182 M * nou hi there, it seems changes have been made to samba (smbd/oplock.c). is http://linux-vserver.org/Problematic_Programs#Samba still correct ? (at least it seems the proposed change in oplock.c is not anymore). any clue ? 1166704083 Q * Aiken Ping timeout: 480 seconds 1166706745 M * daniel_hozac|irssi nou: if you don't change it, do you encounter any problems? 1166706758 N * daniel_hozac|irssi daniel_hozac 1166706973 M * nou daniel_hozac: i haven't tested yet, i'm about to setup vserver in a xen domU. doing some tests would be the next step anyway 1166706975 M * meebey which CAP do I need to allow the usage of RLIMIT_MEMLOCK? 1166706978 M * meebey wodim wants that 1166707116 P * pisco 1166707144 M * daniel_hozac meebey: ccap set_rlimit. 1166707289 M * daniel_hozac Bertl_zZ: just FYI, the bug niol encountered is the one we fixed in 2.0.2.2-rc9. 1166707297 M * meebey hm I dont find that one 1166707300 M * daniel_hozac Bertl_zZ: i.e. the off by one cacct. 1166707306 M * meebey in include/linux/capability.h 1166707332 M * daniel_hozac because i said ccap. 1166707340 M * daniel_hozac not bcap. 1166707342 M * daniel_hozac http://linux-vserver.org/Capabilities_and_Flags 1166707376 M * meebey no way to set that with legacy config? 1166707398 M * daniel_hozac probably not, no. 1166707451 M * meebey ok then I will convert the config first 1166707461 M * meebey 1 0x00000002 SET_RLIMIT Allow setrlimit(2) 1166707464 M * meebey ok, got it 1166707480 M * daniel_hozac depending on how old tools you're using, it might be called rlimit. 1166707485 M * meebey is rlimit also in 2.0? 1166707491 M * daniel_hozac yes. 1166707503 M * meebey k 1166707815 J * \ing ~just@202.99.128.193 1166707932 Q * \ing Quit: Leaving 1166708516 Q * sannes Remote host closed the connection 1166708518 J * sannes ace@har.sagt.no 1166709253 Q * Fire_Egl Quit: ... 1166711116 J * dna ~naucki@p54BCFC9E.dip.t-dialin.net 1166711372 J * Piet hiddenserv@tor.noreply.org 1166712426 J * dna_ ~naucki@p54BCFC9E.dip.t-dialin.net 1166712728 Q * dna Ping timeout: 480 seconds 1166713513 Q * dna_ Ping timeout: 480 seconds 1166714916 J * FireEgl ~FireEgl@adsl-61-147-76.bhm.bellsouth.net 1166714999 Q * FireEgl 1166715065 J * FireEgl ~FireEgl@adsl-61-147-76.bhm.bellsouth.net 1166715065 J * Fire_Egl Sebastian@adsl-61-147-76.bhm.bellsouth.net 1166715072 J * FireEgl_ ~FireEgl@adsl-61-147-76.bhm.bellsouth.net 1166715078 Q * FireEgl Remote host closed the connection 1166715079 Q * FireEgl_ Read error: Connection reset by peer 1166715091 Q * Fire_Egl 1166716426 J * dna ~naucki@p54BCFC9E.dip.t-dialin.net 1166716687 J * FireEgl Proteus@adsl-61-147-76.bhm.bellsouth.net 1166716741 Q * FireEgl 1166718094 M * nebuchadnezzar hello 1166718103 M * daniel_hozac hi 1166718210 M * nebuchadnezzar so, do you have any comment I can forward to my bug report ? 1166718258 M * daniel_hozac well, nothing more than "that's horribly miscompiled" :) 1166718273 M * nebuchadnezzar ok 1166718275 M * nebuchadnezzar thanks 1166718480 M * nebuchadnezzar mail sent 1166718987 J * lilalinux ~plasma@80.69.41.2 1166719177 J * FireEgl Proteus@adsl-61-147-76.bhm.bellsouth.net 1166719206 J * stefani ~stefani@tsipoor.banerian.org 1166719900 Q * rob-84x^ Quit: That's it for today 1166720993 J * bonbons ~bonbons@83.222.37.103 1166722546 J * _mcp ~hightower@wolk-project.de 1166722546 Q * mcp Read error: Connection reset by peer 1166722551 N * _mcp mcp 1166723806 J * eyck ~eyck@nat.nowanet.pl 1166728265 M * matti Hi eyck. 1166728736 N * Bertl_zZ Bertl 1166728740 M * Bertl morning folks! 1166728743 M * daniel_hozac morning Bertl! 1166728754 M * hardwire you guys wanna get crazy? 1166728873 M * Bertl hmm, why would we want to get crazier than we already are? :) 1166728960 A * hardwire was just reading about samsungs non-volitile cached hdd's 1166729135 A * hardwire was pondering a block device or filesystem method to handle this 1166729164 M * hardwire I sort of like the idea of a better unionfs or a CoW block driver that can handle write operations to disk by caching them to flash first 1166729177 M * hardwire I wonder how often the buffer will change as writes consistantly overwrite themselves. 1166729184 M * hardwire like saving a file 100 times over and over. 1166729191 M * hardwire or touching an atime :) 1166729928 Q * mire Read error: Operation timed out 1166730688 J * mire ~mire@173-166-222-85.adsl.verat.net 1166731251 J * rob-84x^ ~rob@submarine.ath.cx 1166732252 M * Bertl daniel_hozac: ah, tx, regarding the niol bug, didn't recognize it 1166732513 J * Wonka_ produziert@chaos.in-kiel.de 1166732539 Q * Wonka Ping timeout: 480 seconds 1166732739 J * Aiken ~james@tooax6-119.dialup.optusnet.com.au 1166732893 M * Wonka_ note to self: "chcontext --xid $xid telinit 0" doesn't stop the vserver, but the host 1166732898 N * Wonka_ Wonka 1166732947 M * Wonka found this out while looking why "vserver $name enter" gave some error message which i have already forgotten :/ 1166732947 M * Bertl yep 1166732953 M * Wonka mind like a sieve 1166732979 M * Bertl problem is, telinit only contacts init via that pipe/socket 1166733002 M * Bertl so, in theory, a chroot in addition should help 1166733003 M * Wonka vnamespace errored somehow... 1166733695 M * Wonka aah 1166733701 M * Wonka problem persists 1166733717 M * Bertl let's hear ... 1166733721 M * Wonka vnamespace: vc_enter_namespace(): Invalid argument 1166733740 M * Wonka vnamespace: vc_enter_namespace(): Invalid argument 1166733743 M * Wonka hrmf 1166733750 M * Wonka while doing "vserver $name enter" 1166733753 M * Bertl what kernel, what tool version? 1166733758 M * Wonka vserver(0xa010000, 0x62, 0, 0x62, 0xb7f50400) = -1 EINVAL (Invalid argument) 1166733788 M * Bertl we fixed such an issue pretty recently 1166733789 Q * jabra Quit: Lost terminal 1166733807 M * Bertl check for a mask = ~0 in vc_enter_space() 1166733816 M * daniel_hozac that's not fixed in any released version. 1166733824 M * Wonka util-vserver 0.30.211-4 1166733826 M * Bertl ah, so only in my tree 1166733833 M * Bertl time to upload new versions then 1166733846 M * Wonka and kernel 2.6.19.1-vs2.2.0-rc5 1166733878 M * daniel_hozac you know you want 0.30.212 for 2.6.19, right? 1166733915 M * Wonka didn't know that mattered that hard 1166733929 M * Wonka so, where'd i check out a fixed version? 1166733946 M * Bertl give me a few minutes 1166734034 M * phreak`` harry: ping 1166734082 J * pisco ~pisco@tor-irc.dnsbl.oftc.net 1166734456 M * daniel_hozac Wonka: pre-0.30.212 utils will have really strange behaviour on 2.6.19+, even when it works. 1166734609 M * Wonka mhmh 1166734687 J * yarihm ~yarihm@84-75-123-221.dclient.hispeed.ch 1166734834 M * pisco wc 1166734837 P * pisco 1166735239 J * pisco ~pisco@p5087C22C.dip0.t-ipconnect.de 1166735374 M * Wonka gotta leave now, will be back later. 1166735921 Q * Aiken Quit: Leaving 1166735986 J * rltns ~relatenes@81.52.161.76 1166736326 J * Aiken ~james@tooax6-119.dialup.optusnet.com.au 1166736345 Q * lilalinux Remote host closed the connection 1166736620 J * niol ~niol@sousmonlit.dyndns.org 1166736828 M * niol hi again 1166736864 Q * bonbons Quit: Leaving 1166736893 M * daniel_hozac hello 1166736962 M * niol Bertl: I tested against the bug I encountered with vanilla 2.6.19, vs2.2.0-rc5 and the bug I was talking about (debian #402743) seems fixed 1166736988 M * niol (I could not reproduce) 1166737021 M * kevinp Bertl: I know we have talked about this before, but I swear the only servers that I ever have my ssh session time out on are vservers. I'm connected to all my servers through a LAN, so I really don't think it is a network timeout problem. Has anyone else ever complained of this? 1166737056 M * daniel_hozac niol: it should be fixed in 2.0.2.2-rc9+. 1166737059 M * Aiken I have had ssh connections time out on normal machines 1166737101 M * daniel_hozac kevinp: time out as in connection timed out, or what? 1166737258 M * kevinp yeah, the session will hang and then several minutes later I will get disconnected error 1166737320 M * kevinp "Read from remote host vsmail1: Connection timed out. Connection to vsmail1 closed." 1166737538 J * Piet_ hiddenserv@tor.noreply.org 1166737649 M * niol daniel_hozac: what would be your advice for fixing this in etch (as it is frozen and you know how debian is)? Extract the fix from your history or upgrade to vs2.0.0.2 as debian etch uses 2.0.0.2rc6? 1166737686 M * daniel_hozac kevinp: and during the hang, you can establish another connection? 1166737743 M * daniel_hozac niol: waldi knows about it, i guess he'll fix it soon. 1166737744 T * Bertl http://linux-vserver.org/ | latest stable 2.0.2.1, 2.0.3-rc1, 2.2.0-rc6, devel 2.1.1.7.1, 2.3.0.6, stable+grsec 2.0.2.1, devel+grsec 2.1.1 | util-vserver-0.30.212 | libvserver-1.0.2 & vserver-utils-1.0.3 | He who asks a question is a fool for a minute; he who doesn't ask is a fool for a lifetime -- share the gained knowledge on the Wiki, and we'll forget about the minute ;) 1166737764 M * daniel_hozac Bertl: yay, 5 part version numbers! ;) 1166737764 M * Bertl niol: thanks for the feedback 1166737777 M * Aiken Bertl I love the timing, my uptime with 2.2.0-rc5 is only 29 minutes 1166737777 M * Bertl daniel_hozac: yeah :) 1166737790 Q * Piet Ping timeout: 480 seconds 1166737794 M * Bertl Aiken: sorry, but lol! 1166737848 M * Aiken oh well, another kernel shortly :) 1166737943 M * niol ok thanks all, I justed wanted to ensure that this would be fixed 1166737955 M * daniel_hozac Bertl: initial GFS2 support? 1166737978 M * Bertl very basic 1166737991 M * Bertl but yeah, I'm working on it 1166738025 M * Bertl well, I lied, currently I'm trying to flash a broken (soldered in) bios via parallel port 1166738151 M * daniel_hozac sounds interesting... any success? 1166738176 M * Bertl yeah, I can already identify the chip and read the current bios 1166738194 M * Bertl via the 'proprietary' FWH interface (5 lines + clock) 1166738244 M * daniel_hozac cool. 1166738447 Q * rltns Quit: Leaving 1166738518 M * niol anyway thanks a lot for the help, see ya! 1166738617 Q * niol Quit: leaving 1166740471 M * kevinp daniel_hozac: sorry I missed your response, yeah other sessions will stay open and work and I can create new sessions just fine. 1166740516 M * micah daniel_hozac: does the rsync build-method implement all of what vserver-copy used to for legacy? I see that vserver-copy is still around, although its a legacy only script 1166740537 M * kevinp just random windows/sessions will hang right in the middle of using them. pretty annoying. 1166740599 M * micah daniel_hozac: the vserver-debianutils also contains a 'dupvserver' script, which does something similar 1166740622 M * daniel_hozac micah: i have no idea what vserver-copy does :) 1166740675 M * micah daniel_hozac: me neither until I started looking at vserver-debianutils to see what could be brought into util-vserver and then I noticed that 1166740703 M * micah daniel_hozac: there is even a man page for vserver-copy... it essentially does an rsync 1166740723 M * daniel_hozac yeah, looks like build -m rsync should do everything it does. 1166740728 M * daniel_hozac (of the things that make sense, at least) 1166740833 M * micah i wonder if 'build -m rsync' should also be known as 'build -m copy | build -m duplicate' since people seem to think of the purpose rather than the method 1166740875 M * daniel_hozac no. 1166740888 M * daniel_hozac i have a -m clone on my TODO-list. 1166740899 M * daniel_hozac but it would use a special helper. 1166740913 M * daniel_hozac that would link unified/hashified files, and just copy the others. 1166740921 M * micah great, I first was looking for -m clone in util-vserver since I thought it was already there 1166740937 M * daniel_hozac the first -m clone was just a cp -a. 1166740941 M * daniel_hozac i.e. a hack. 1166740957 M * micah it used to exist, but now doesn't, right? 1166740971 M * daniel_hozac it existed as a patch. 1166740973 J * MHGuest787 ~MHGuest78@cpe-071-075-226-103.carolina.res.rr.com 1166740988 M * micah ok, I knew I had seen it somewhere 1166740991 M * daniel_hozac (but not one i endorsed, as it was a hack) 1166741007 N * MHGuest787 DragonSlayer 1166741023 M * micah ok, I'm just looking at the vserver-debianutils stuff to see how much of it is already in util-vserver and what needs to be pulled in 1166741028 A * Hollow wonders when 2.1.1.7.2.3.1.2 will be released ;) 1166741037 M * daniel_hozac hehehe. 1166741048 M * micah so I'm guessing that the util-vserver vserver-copy and associated man pages can go away 1166741065 M * daniel_hozac it's already tagged as legacy :) 1166741090 M * micah ok 1166741098 M * micah where is such tagging? 1166741115 M * daniel_hozac the fact it's in script/legacy should be a hint. 1166741123 Q * DragonSlayer 1166741125 M * micah yeah :) 1166741130 M * daniel_hozac and contrib/manifest.dat.pathsubst shows the split of packages that the RPMs use. 1166741145 M * Hollow puntlegacy++ 1166741172 M * daniel_hozac yeah, i'm starting to lean towards that... 1166741220 M * daniel_hozac it's not like anyone's maintaining it :) 1166741467 Q * FireEgl Quit: ... 1166741519 M * micah daniel_hozac: do the RPMs build a separate legacy package? 1166741544 M * daniel_hozac yes. 1166741548 M * Wonka re 1166741881 M * Wonka so, i'm building 2.2.0-rc6 now 1166741905 M * daniel_hozac it should make your older utils work. 1166741991 M * Wonka sometimes, i am quite annoyed by debian being so slow... 1166742022 M * daniel_hozac i guess waldi has other bugs to process :) 1166742044 M * Wonka i didn't mean any single developer 1166742084 M * Wonka example: every distro and their grandmother has beryl packages, only debian hasn't.. 1166742093 M * daniel_hozac hehe. 1166742138 P * stefani I'm Parting (the water) 1166742179 A * Wonka corrects himself: Wonka doesn't build yet, Wonka is still cp-ing and patch-ing 1166742186 M * Wonka interdiff-ing, exactly 1166742366 M * Wonka kernel/vserver/Kconfig:233: unknown option "intxi" 1166742368 M * Wonka wtf? 1166742395 M * Wonka vi error? 1166742409 M * daniel_hozac huh? 1166742423 M * daniel_hozac doh, you're right. 1166742456 M * daniel_hozac and i missed that twice... 1166742471 M * daniel_hozac Bertl: fix in-place? 1166742565 Q * pisco Quit: leaving 1166742783 M * Bertl yep, sec 1166742861 M * Bertl okay, should be fine now 1166743067 J * Guy- zMfe8fcgs1@chardonnay.math.bme.hu 1166743072 M * Guy- hi 1166743083 M * Bertl welcome Guy-! 1166743117 M * Guy- hey Bertl, it's always nice to see the traditional Austrian Gastfreundschaft being kept up :) 1166743146 M * Wonka *make* 1166743252 M * Guy- for a new vserver installation, based around a 2.6.19.1, which version of vserver should I use? 2.0, 2.1, 2.2 or 2.3? I don't mind using a development version, as such, but I'd like it to compile and mostly work without much fuss :) 1166743301 M * daniel_hozac 2.1, 2.2 and 2.3 are the only ones available for 2.6.19+. 1166743309 M * daniel_hozac 2.2 is probably a good idea though. 1166743338 M * Guy- 2.2.0-rc6 then, right? 1166743353 M * Bertl yep, 2.2 is the upcoming stable which hast almost all of the current devel features 1166743360 M * Wonka its the newest, with some bugs fixed, yes 1166743397 M * Guy- OK, thanks 1166744428 M * Guy- what's this CONFIG_BLK_DEV_VROOT? The associated help doesn't really tell me much 1166744438 M * Guy- Saying Y here will allow you to use quota/fs ioctls on a shared 1166744438 M * Guy- partition within a virtual server without compromising security. 1166744464 M * daniel_hozac a shared partition? i guess we need to remove that. 1166744485 M * daniel_hozac it's for letting guests manage quota in a secure way. 1166744507 M * daniel_hozac the vroot device acts as a proxy that only lets the quota ioctls through. 1166744508 M * Guy- so if I don't want separate quota support in my virtual contexts, I don't need this option, right? 1166744530 M * daniel_hozac no. 1166744555 M * Guy- what other ioctls would apply, that are blocked, but would be dangerous to allow? 1166744576 M * daniel_hozac guests don't have the device nodes at all generally. 1166744668 M * Guy- I guess I won't really understand what this option does without knowing how the quota system is implemented... 1166744832 J * FireEgl ~FireEgl@adsl-61-147-76.bhm.bellsouth.net 1166745166 P * Kerberos satan told me to 1166745425 Q * Wonka Read error: Connection reset by peer 1166745454 Q * meandtheshell Quit: Leaving. 1166745470 J * Wonka produziert@chaos.in-kiel.de