1249344249 J * imcsk8 ~ichavero@189.155.85.45 1249346589 J * Elton04246 ~Delphi@201008145180.user.veloxzone.com.br 1249346769 Q * imcsk8 Quit: This computer has gone to sleep 1249347041 J * scientes ~scientes@97-113-166-22.tukw.qwest.net 1249347448 Q * Elton04246 Read error: Connection reset by peer 1249347615 J * Elton02551 ~Delphi@201008145180.user.veloxzone.com.br 1249347986 Q * Elton02551 Remote host closed the connection 1249348163 J * Elton01776 ~Delphi@201008145180.user.veloxzone.com.br 1249348443 Q * Elton01776 Read error: Connection reset by peer 1249349034 J * Elton02578 ~Delphi@201008145180.user.veloxzone.com.br 1249349056 Q * Elton02578 Remote host closed the connection 1249349305 J * Elton03510 ~Delphi@201008145180.user.veloxzone.com.br 1249349360 Q * Elton03510 Read error: Connection reset by peer 1249349543 J * Elton06945 ~Delphi@201008145180.user.veloxzone.com.br 1249349672 Q * Elton06945 Read error: Connection reset by peer 1249349765 F * ChanServ +o Bertl 1249349854 Q * gnarface Remote host closed the connection 1249350370 J * Elton07774 ~Delphi@201008145180.user.veloxzone.com.br 1249350539 F * Bertl +b *!*Delphi@*.user.veloxzone.com.br 1249350539 K Elton07774 Bertl please fix your client/network 1249354665 Q * asl Quit: Lost terminal 1249355385 Q * SauLus Ping timeout: 480 seconds 1249355586 J * saulus ~saulus@c207172.adsl.hansenet.de 1249359736 M * Bertl off to bed now ... have a good one everyone! 1249359740 N * Bertl Bertl_zZ 1249360691 J * geb ~geb@AOrleans-253-1-64-186.w92-140.abo.wanadoo.fr 1249360973 M * geb hi 1249361096 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1249361418 Q * ghislainocfs21 Ping timeout: 480 seconds 1249361536 Q * hparker Quit: Read error: 104 (Peer reset by connection) 1249362614 J * sharkjaw ~gab@149-49-95.oke2-bras6.adsl.tele2.no 1249365595 J * doener ~doener@i59F57B25.versanet.de 1249365786 Q * nenolod Quit: my eyes cannot compute this misery. 1249366643 J * nenolod nenolod@petrie.dereferenced.org 1249367963 Q * ghislainocfs2 Quit: Leaving. 1249369242 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1249370380 J * BenG ~bengreen@94-169-110-10.cable.ubr22.aztw.blueyonder.co.uk 1249370580 Q * geb Ping timeout: 480 seconds 1249371290 M * theocrite 2 1249371540 M * pmjdebru1jn I'm having an odd issue with Samba where nmbd gets confused: http://pastebin.com/d6596d0b1 1249371555 M * pmjdebru1jn it seems to be only happening in our vservers, anybody a clue what could be wrong? 1249372951 Q * puck Ping timeout: 480 seconds 1249373095 J * puck ~puck@leibniz.catalyst.net.nz 1249373634 J * davidkarban ~david@193.85.217.71 1249374164 M * pmjdebru1jn hmm having nmblookup lookup directly to an IP works 1249374167 M * pmjdebru1jn just not via broadcast 1249374244 J * limon ~limon@94.54.237.152 1249374252 M * limon hi how can solve vlimit: fstat("/etc/vservers/vdrup/rlimits"): Permission denied 1249374255 M * limon ? 1249374933 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d 1249375387 J * gnuk ~F404ror@pla93-3-82-240-11-251.fbx.proxad.net 1249375973 M * pmjdebru1jn limon: uhm 1249375981 M * pmjdebru1jn limon: check unix permissions? 1249376298 M * limon pmjdebru1jn: with root? 1249376324 M * blathijs limon: What are you trying to do? 1249376342 M * limon blathijs: vserver vdrup start 1249376351 Q * puck Ping timeout: 480 seconds 1249376372 J * puck ~puck@leibniz.catalyst.net.nz 1249376417 M * blathijs limon: I'd check the permissions of the /etc/vservers/vdrup directory 1249376984 M * limon blathijs: 755 1249377001 M * blathijs Sounds okay... 1249377013 M * blathijs And fstatting isn't something that requires extra privileges AFAIK 1249377028 M * blathijs limon: You might try running strace, to see what is happening exactly 1249377078 M * _nono_ hi folks 1249377119 M * _nono_ I have an issue with vserver and iproute2 1249377175 M * _nono_ basically, I use a pre-start script to create an ad-hoc default route for a vserver, and when I stop the vserver the route goes away even though I don't explicitely remove it 1249377184 M * _nono_ see http://files.glou.org/typescript-vserver-iproute2.txt 1249377194 M * _nono_ is this expected behavior? 1249377408 M * BWare Is the interface that is used for routing still there ? 1249377451 M * BWare if not, it's expected behaviour... even on kernels without vserver patch ;) 1249377631 M * BWare i also notice you delete the rule (from... table 102) ... IIRC that also clears the table if it's the last rule for that table 1249377649 M * _nono_ the interface is still there 1249377660 Q * ktwilight__ Read error: Connection reset by peer 1249377665 M * _nono_ and no, removing the last rule does not clear the table 1249377690 M * _nono_ or at least it is not supposed to 1249377771 J * ktwilight__ ~keliew@155.171-247-81.adsl-dyn.isp.belgacom.be 1249377789 M * _nono_ I just checked, when I create then remove a rule "by hand" on the same machine, it does not clear the table 1249377868 M * _nono_ http://files.glou.org/typescript-iproute2-no-vserver.txt 1249377886 Q * balbir_ Read error: Connection reset by peer 1249377929 M * _nono_ if it matters, kernel is 2.6.30.2-vs2.3.0.36.14pre4 and util-vserver is svn rev 2844 1249377995 J * C14r ~C14r@mail.cipworx.de 1249378015 M * BWare eth0 is still there after a vserver stop ? 1249378046 M * _nono_ I don't use eth0, I have a bridge interface 1249378068 M * BWare default via 129.102.6.66 dev eth0 1249378118 M * _nono_ oh, sorry, I used eth0 for my second test 1249378163 J * dna ~dna@55-197-103-86.dynamic.dsl.tng.de 1249378166 M * _nono_ my vserver IPs are bound to bridge interfaces, the aim is to distribute them between several vlans 1249378178 M * BWare check what interface is specified for default after starting vserver; then stop the vserver and see if that interface is still up and configured 1249378194 M * BWare if not, then it's expected behaviour ;) 1249378198 M * _nono_ I will try the "no-vserver" case on my bridge interface, in case it changes anything 1249378229 M * _nono_ but in the vserver case, the bridge interface is still here, I already checked this 1249378242 M * BWare configured and showing 'UP' ? 1249378298 M * BWare if there's no IP address assigned to the interface any routes to the interface/address are removed 1249378318 M * BWare if the interface is in a 'DOWN' state, IIRC the same applies 1249378455 M * _nono_ 5: br102: mtu 1500 qdisc noqueue 1249378472 M * _nono_ but it does not have an IP address 1249378548 M * BWare then the route is removed ;) 1249378554 M * _nono_ yes, that was it 1249378560 M * _nono_ thanks for your help! 1249378564 M * BWare n/p 1249378669 N * Bertl_zZ Bertl 1249378677 M * Bertl morning folks! 1249378682 M * BWare check the flower page, iirc there is a way to keep the interface configured after shutting down the vserver 1249378685 M * BWare morning bertl 1249378816 J * balbir_ ~balbir@122.172.13.136 1249378955 M * _nono_ well, now I know how it is supposed to bahve, I can write my pre-start / post-stop scripts accordingly, no big deal 1249379002 M * BWare oke ;) 1249379082 Q * richi_ Remote host closed the connection 1249380654 M * ghislainocfs2 bon je vais manger a toute 1249380658 M * ghislainocfs2 oups soirry 1249381102 M * Bertl we might use it against you at some point :) 1249381836 Q * derjohn Read error: Connection reset by peer 1249382142 J * geb ~geb@AOrleans-253-1-12-101.w92-140.abo.wanadoo.fr 1249382465 J * ghislainocfs21 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1249382678 J * derjohn ~derjohn@80.69.41.3 1249382693 Q * Swordsman Read error: Connection reset by peer 1249382726 Q * Supaplex Ping timeout: 480 seconds 1249382775 Q * ghislainocfs2 Ping timeout: 480 seconds 1249383298 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1249383610 Q * ghislainocfs21 Ping timeout: 480 seconds 1249383779 J * ghislainocfs21 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1249383877 J * ncopa ~ncopa@90.149.199.29 1249384050 Q * ghislainocfs2 Ping timeout: 480 seconds 1249384160 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1249384440 Q * ghislainocfs21 Ping timeout: 480 seconds 1249385072 Q * BenG Quit: I Leave 1249385270 Q * ghislainocfs2 Ping timeout: 480 seconds 1249385454 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1249385960 J * mib_9o2az3ve 57046096@webchat.mibbit.com 1249385997 M * mib_9o2az3ve hello 1249386015 M * mib_9o2az3ve there is none? 1249386021 Q * mib_9o2az3ve 1249386331 J * BenG ~bengreen@94-169-110-10.cable.ubr22.aztw.blueyonder.co.uk 1249386389 M * Bertl attention span of a fly :) 1249386417 M * Bertl ghislainocfs2: please try to fix your connection too :) 1249386658 N * pmenier pmenier_off 1249387164 Q * bonbons Quit: Leaving 1249387690 Q * BenG Quit: I Leave 1249388116 Q * ktwilight__ Remote host closed the connection 1249388141 J * ktwilight__ ~keliew@155.171-247-81.adsl-dyn.isp.belgacom.be 1249388301 J * ghislainocfs21 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1249388515 Q * ghislainocfs2 Ping timeout: 480 seconds 1249388526 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d 1249388583 Q * nou Ping timeout: 480 seconds 1249389161 M * pmjdebru1jn anybody here running Samba in a current (2.6.27+) vserver? 1249389424 M * Bertl do you expect or experience any issues, or is it just curiosity? 1249389485 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1249389626 M * pmjdebru1jn no 1249389636 M * pmjdebru1jn somehow my broadcast name resolving is broken 1249389646 M * pmjdebru1jn directed resolving seems to work 1249389686 M * daniel_hozac i do, but i always disable nmbd. 1249389695 J * nou Chaton@causse.larzac.fr.eu.org 1249389745 M * pmjdebru1jn huh? 1249389754 M * pmjdebru1jn daniel_hozac: because? 1249389764 M * pmjdebru1jn anyway we're running a PDC, so nmbd is pretty much required 1249389776 M * daniel_hozac because i have DNS. 1249389778 M * pmjdebru1jn we never had this issue with the previous vserver patch 1249389796 M * pmjdebru1jn daniel_hozac: we don't need full DNS in this setup 1249389802 J * hparker ~hparker@2001:470:1f0f:32c:290:96ff:fe50:40fa 1249389805 Q * ghislainocfs21 Ping timeout: 480 seconds 1249389809 M * pmjdebru1jn daniel_hozac: it would incur massive extra maintenance... 1249389820 M * Bertl so, how is it broken? 1249389830 M * pmjdebru1jn Bertl: it doesn't resolve anymore 1249389836 M * Bertl i.e. what requests/responses do you get/expect? 1249389865 M * pmjdebru1jn nmblookup NAME doesn't return anything 1249389868 M * pmjdebru1jn it just fails 1249389873 M * fback pmjdebru1jn: i had similar issues 1249389880 M * pmjdebru1jn somehow, it only goes wrong a couple of days, after starting the daemons 1249389884 M * pmjdebru1jn which is odd 1249389890 M * fback pmjdebru1jn: and it was single ip special case 1249389892 M * Bertl try to do a tcpdump of the netbios requests 1249389896 M * pmjdebru1jn I must note I'm using another version of samba as well 1249389904 M * pmjdebru1jn Bertl: I'll try that 1249389928 J * docelic ~docelic@78.134.200.146 1249389978 M * pmjdebru1jn can I tcpdump _in_ a vserver? 1249389978 M * Bertl maybe even run nmbd interactively with debugging enabled 1249389987 M * Bertl nope, you want to tcpdump on the host 1249389992 M * pmjdebru1jn ugh 1249389993 M * pmjdebru1jn hmm ok 1249390001 M * pmjdebru1jn http://pastebin.com/d6596d0b1 1249390004 M * pmjdebru1jn that's my log.nmbd 1249390007 M * Bertl but you can do it from a chroot :) 1249390066 M * Bertl 10.150.39.224 is the nmbd address? 1249390125 M * pmjdebru1jn yeah 1249390148 M * pmjdebru1jn somehow, when it not broken in the first few days... when I request with nmblookup, I get two responses instead of one 1249390176 M * Bertl is that ip assigned to the guest? 1249390221 M * pmjdebru1jn http://pastebin.com/d4efe1586 1249390223 M * pmjdebru1jn Bertl: yeah 1249390241 M * Bertl is it the only ip assigned to that guest? 1249390475 M * pmjdebru1jn yes 1249390480 M * pmjdebru1jn except for loopback of course 1249390519 M * Bertl and is the single_ip special casing disabled? 1249390573 M * pmjdebru1jn huh? 1249390585 M * pmjdebru1jn I guess I missed something? 1249390650 M * Bertl well, if you want to use the loopback IP, you need to disable the single_ip special casing, which usually is on by default 1249390666 M * Bertl otherwise all addresses will be mapped to the single IP on binding 1249390785 M * pmjdebru1jn I don't think we set that 1249390793 M * pmjdebru1jn how can I see if it's on by default? 1249390871 M * pmjdebru1jn can I explicitly disable it? does prefixing a ~disable it? 1249390925 M * Bertl yep, you can see it in the nflags for your guest (network context) 1249390936 M * Bertl and you can disable by using ~single_ip 1249390995 M * daniel_hozac try e.g. nattribute --get --nid 1249391018 J * VavaR ~vava@p5496E15C.dip.t-dialin.net 1249391056 M * pmjdebru1jn do caps matter? 1249391106 Q * r Read error: Operation timed out 1249391107 M * pmjdebru1jn ok they don't 1249391116 M * pmjdebru1jn single_ip is on by default 1249391121 M * Bertl caps as in capitals, not capablities :) 1249391121 M * pmjdebru1jn I've just disabled it on a test machine 1249391130 M * pmjdebru1jn Bertl: yeah, that's what I ment... sorry 1249391355 M * pmjdebru1jn the logs eems to change a bit 1249391387 M * pmjdebru1jn Bertl: wouldn't it be sane behaviour to automatically disable single_ip when a loopback is provided? 1249391478 M * daniel_hozac why did you configure both in the kernel? 1249391504 M * pmjdebru1jn hmmm 1249391508 M * pmjdebru1jn daniel_hozac: did I? 1249391520 M * daniel_hozac if you built the kernel yourself... 1249391523 M * pmjdebru1jn daniel_hozac: yeah 1249391532 M * pmjdebru1jn daniel_hozac: I probably did realize the consequences then... 1249391552 M * daniel_hozac it says enabling the single IP special casing won't work with loopback addresses. 1249391566 M * pmjdebru1jn daniel_hozac: I probably didn't read the help then... 1249391577 M * pmjdebru1jn I'll check 1249391590 M * pmjdebru1jn daniel_hozac: the previous did should have been a didn't as well btw :) 1249391700 M * pmjdebru1jn yep, I enabled both 1249391715 M * pmjdebru1jn daniel_hozac, Bertl feel free to slap me over the head with something... 1249391734 M * Bertl no need, I guess you learned the lesson :) 1249391770 M * pmjdebru1jn the hard way 1249391773 M * pmjdebru1jn but... 1249391799 M * pmjdebru1jn isn't there a construct in Kconfig which disappears certain options when another option is disabled, prevent people from making such a mistake 1249391810 M * pmjdebru1jn basically making it pmjdebru1jn-proof :) 1249391841 M * Bertl sure, but the default is to enable it, so hiding it wouldn't have helped you 1249391955 M * fback pmjdebru1jn: it was my suggestion too, when it bit me some time ago 1249391983 M * fback pmjdebru1jn: but now i have doubts, if it should be automatically disabled on that level 1249392106 M * pmjdebru1jn either way some people will get bitten 1249392109 M * Bertl it is an optimization, with tradition, i.e. Linux-VServer has used this optimization for a long time now 1249392146 M * Bertl when we introduced the complete loopback remapping, this flag, and the kernel default, were added 1249392156 M * fback pmjdebru1jn: maybe some warning when starting guest system would be better 1249392180 M * Bertl it is a perfect setup with and without, nothing to warn about 1249392185 M * pmjdebru1jn "Dear admin, you did something terribly stupid, please... " 1249392187 M * BWare or some pointers in the wiki ;) 1249392207 M * Bertl BWare: wiki is a good idea, but I think we already have it in several places 1249392235 M * Bertl pmjdebru1jn: like warning 'Dear admin, using private IPs will not allow you to visit the internet without nat'? 1249392237 M * fback Bertl: "you have enabled both auto loopback and single ip special case. be warned!" 1249392272 M * Bertl be warned of what? 1249392274 M * sid3windr s/be warned/you suck/ 1249392274 M * sid3windr :D 1249392293 M * fback Bertl: you may get into troubles ;) 1249392321 M * Bertl something like: 'you have enabled both auto loopback and single ip special casing, be warned that it will exactly do what you asked for!' :) 1249392359 M * fback Bertl: yes, that's my point 1249392378 M * fback Bertl: I'm one of many who realised this after it bite 1249392385 M * fback and wasted your time 1249392389 M * fback ;) 1249392409 M * Bertl well, talk to daniel_hozac, I doubt he will consider this a sensible warning ... but maybe I'm wrong :) 1249392427 M * pmjdebru1jn Bertl: "you've asked for something that's not sensible" 1249392438 M * Bertl well, that would be wrong 1249392446 M * Bertl as it makes perfect sense to have both enabled 1249392448 M * fback pmjdebru1jn: that's not not sensible :) 1249392467 M * pmjdebru1jn Bertl: huh? 1249392472 M * fback you just should be aware of the consequences :) 1249392910 M * Bertl I am toying with the idea to disable the default, or to auto-disable the single IP, when the lback address doesn't match the single IP 1249392919 M * elesouef Hi there. I don't know if it is due to debian's dupvserver but when I start a duplicated vserver via vserver vserver2 start, the original copy of the vserver loses its name in vserver-stat. Normal ? 1249392946 M * Bertl elesouef: no idea what dupvserver is, but I'd suggest not to use it 1249392976 M * Bertl (probably part of the outdate and known-to-be broken/harmful debian-vserverutils/tools) 1249392999 M * elesouef Bertl: as far as I know it is using rsync to duplicate vservers. 1249393021 M * Bertl use 'vserver - build -m rsync' then 1249393046 M * Bertl but better would be 'vserver - build -m clone' as it will create links for hashed guests 1249393053 M * elesouef By the way, what can cause a vserver to "lose" its name in vserver-stat (thus making it impossible to enter via vserver ... enter) 1249393066 M * daniel_hozac removal of the run file. 1249393084 M * elesouef Bertl: understood I'll use it next time. 1249393125 M * Bertl most likely your problems (including those with the disappearing name) will go away then 1249393200 M * elesouef daniel_hozac: you're right, the run file has been removed 1249393462 M * Bertl pmjdebru1jn,fback: another idea was to use the single IP for the lback address, when auto-lback is enabled, which would give exactly the same behaviour than with older patches 1249393482 M * Bertl daniel_hozac: maybe that could be something done from within util-vserver though? 1249393502 M * Bertl (as it exactly knows how many IPs the guest will get) 1249393516 M * pmjdebru1jn hmm I'm still getting the double reply though 1249393526 M * pmjdebru1jn even though with the SINGLE_IP option disabled in the kernel 1249393541 M * Bertl tcpdump it for me, and upload the output 1249393548 M * Bertl i.e. request and the two responses 1249393569 M * Bertl (or requests, if there are more than one :) 1249394161 M * Bertl nap attack ... bbl 1249394163 N * Bertl Bertl_zZ 1249394401 Q * sharkjaw Remote host closed the connection 1249394469 M * pmjdebru1jn hmm but a plain tcpdump won't included traffic over the vserver specific loopback will it? 1249394532 M * daniel_hozac if you run it on -i lo, sure it will. 1249394551 M * pmjdebru1jn aren't the vserver lo specific to each vserver? 1249394575 M * daniel_hozac no. 1249394605 M * daniel_hozac Linux-VServer does IP address isolation, not virtual interfaces. 1249394708 M * pmjdebru1jn daniel_hozac: I'm on 2.6.27.x-vs 1249394708 M * geb you will see that the address are a bit specific 1249394756 M * pmjdebru1jn they're all 127.0.0.1 here 1249394767 M * daniel_hozac nope, they're not. 1249394772 M * daniel_hozac they just appear to be. 1249394774 M * pmjdebru1jn oh 1249394775 M * BWare :) 1249394816 M * geb iptables -A INPUT -i lo -d ! 127.0.0.1 -j VSERVERS :) 1249394839 M * daniel_hozac well, that's not necessarily true. 1249394864 M * daniel_hozac lo will also see all traffic destined to other IP addresses on the host. 1249394893 A * geb takes notes :) 1249395033 M * geb do you have an example ? you mean that if i have an eth1 , a tun0 , i can use something like route add $tun0_ip_range lo ? 1249395042 M * daniel_hozac no. 1249395047 M * daniel_hozac you don't need any routes whatsoever. 1249395080 M * daniel_hozac traffic going to an IP address assigned to the host will use lo. 1249395106 M * daniel_hozac so if your tun0 is 1.2.3.4, traffic going to 1.2.3.4 will go over lo. 1249395134 M * geb yeah, so lo is used for traffic going to vserver , but also from , that's what you mean ? 1249395183 M * daniel_hozac lo is used for vserver-to-vserver traffic (regardless of if it's the same vserver), and host-to-vserver, and vserver-to-host, and host-to-host. 1249395292 M * geb ok i just misunderstood 1249395302 M * geb :) 1249395342 M * geb i just the previous iptables rule to filter traffic from/to vservers , that should not impact host to host traffic, right ? 1249395365 M * daniel_hozac that rule only elimiates the host-to-host traffic to 127.0.0.1 1249395376 M * daniel_hozac if the host connects to its public IP address, that rule won't cover it. 1249395446 M * daniel_hozac personally, i don't use interface based rules for my guests. since Linux-VServer is based on IP addresses, so are my rules. 1249395476 M * daniel_hozac thus i use the same rules for vserver-to-vserver traffic as i do for external access to them. 1249395521 M * theocrite Bertl_zZ: elesouef I do not think vserver-debiantools is involved. I had the bug with the usual tools (vserver-utils). But Debian is indeed probably involved. 1249395531 M * theocrite ('night Bertl_zZ btw) 1249395719 M * elesouef theocrite: In fact, I think we have to rebuild a new kernel with the appropriate patches... 1249395765 M * daniel_hozac that certainly doesn't make things worse, but that's not going to affect your problem. 1249395936 M * geb oh that may explain why i am unable to ping my eth0 interface, thanks , i was thinking that the ping use this interface (like if -I eth0 was implicit) 1249395976 M * geb but what to you mean by "is based on IP addresses" , last time i checked i did see some traffic from/to 127.X.Y.Z ? 1249396008 M * daniel_hozac yes. 1249396012 M * theocrite elesouef: i'm afraid so. Unless there is a way to relink the run file to the /var/run/vservers/ file or something ? 1249396030 M * daniel_hozac my INPUT rules for each guest are for their public IP addresses, and 127..1. 1249396204 A * geb notes the :) 1249397701 J * ghislainocfs21 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1249398008 Q * ghislainocfs2 Ping timeout: 480 seconds 1249398217 J * dowdle ~dowdle@scott.coe.montana.edu 1249398243 Q * MooingLemur Quit: leaving 1249398269 J * MooingLemur ~troy@shells195.pinchaser.com 1249398765 Q * balbir_ Read error: Connection reset by peer 1249399396 J * mxs mxs@p4FCCB433.dip.t-dialin.net 1249399632 J * balbir_ ~balbir@122.172.38.65 1249399694 Q * mxs_ Ping timeout: 480 seconds 1249401780 J * imcsk8 ~ichavero@nat.ti.uach.mx 1249401989 N * Bertl_zZ Bertl 1249401994 M * Bertl back now ... 1249402128 J * Elton04069 ~Delphi@189.82.166.192 1249402147 Q * davidkarban Quit: Ex-Chat 1249403135 Q * Elton04069 Read error: Connection reset by peer 1249403579 M * limon cls 1249403842 J * ousado ~johnny@p5B3C105F.dip0.t-ipconnect.de 1249404278 Q * ousado__ Ping timeout: 480 seconds 1249404503 Q * gnuk Quit: NoFeature 1249404669 J * ghislainocfs2 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1249404935 Q * ghislainocfs21 Ping timeout: 480 seconds 1249406374 Q * geb Ping timeout: 480 seconds 1249406929 J * geb ~geb@AOrleans-157-1-85-181.w90-20.abo.wanadoo.fr 1249407666 Q * geb Ping timeout: 480 seconds 1249408136 J * Chimpbama ~PC4@201.171.1.78.dsl.dyn.telnor.net 1249408211 J * geb ~geb@AOrleans-253-1-34-68.w92-140.abo.wanadoo.fr 1249408280 Q * Chimpbama autokilled: spammer. Mail support@oftc.net with questions (2009-08-04 17:51:20) 1249409076 Q * geb Ping timeout: 480 seconds 1249409218 Q * scientes Ping timeout: 480 seconds 1249409273 Q * hparker Quit: Read error: 104 (Peer reset by connection) 1249409621 J * geb ~geb@AOrleans-253-1-7-139.w90-24.abo.wanadoo.fr 1249410188 Q * geb Ping timeout: 480 seconds 1249410810 J * Kmos ~gothicx@kmos.user.oftc.net 1249410865 J * geb ~geb@AOrleans-253-1-2-245.w90-24.abo.wanadoo.fr 1249411041 Q * Hunger Remote host closed the connection 1249411241 Q * limon Quit: leaving 1249411435 J * Hunger ~Hunger@Hunger.hu 1249413430 Q * geb Quit: / 1249418305 J * Supaplex ~supaplex@166.70.62.193 1249419945 Q * dna Quit: Verlassend 1249421556 J * ghislainocfs21 ~Ghislain@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1249421865 Q * ghislainocfs2 Ping timeout: 480 seconds 1249424236 Q * imcsk8 Ping timeout: 480 seconds 1249424248 Q * nkukard Ping timeout: 480 seconds 1249424305 J * imcsk8 ~ichavero@evdomip-31-68.iusacell.net 1249424778 J * hparker ~hparker@2001:470:1f0f:32c:290:96ff:fe50:40fa 1249424920 J * nkukard ~nkukard@196.212.73.74 1249425745 Q * nkukard Ping timeout: 480 seconds 1249425945 J * nkukard ~nkukard@196.212.73.74 1249427201 Q * Kmos Quit: return unless user.signoff? 1249427960 Q * docelic Read error: Connection reset by peer 1249429725 Q * imcsk8 Read error: Connection reset by peer 1249429949 Q * dowdle Remote host closed the connection