1178930147 Q * FireEgl Read error: Connection reset by peer 1178930966 J * FireEgl FireEgl@Sebastian.Atlantica.CJB.Net 1178930989 J * Piet_ hiddenserv@tor.noreply.org 1178931404 Q * Piet Ping timeout: 480 seconds 1178933735 Q * yarihm Quit: Leaving 1178935095 Q * Piet_ Quit: Piet_ 1178937180 Q * FireEgl Ping timeout: 480 seconds 1178937260 N * ensc Guest30 1178937270 J * ensc ~irc-ensc@p54B4DFB7.dip.t-dialin.net 1178937302 Q * lilalinux_ Ping timeout: 480 seconds 1178937379 Q * Guest30 Ping timeout: 480 seconds 1178943865 J * FireEgl FireEgl@Sebastian.Tcldrop.Com 1178944465 Q * FireEgl Ping timeout: 480 seconds 1178947883 J * FireEgl FireEgl@4.0.0.0.1.0.0.0.c.d.4.8.0.c.5.0.1.0.0.2.ip6.arpa 1178949485 Q * hardwire Ping timeout: 480 seconds 1178949657 J * micah_ ~micah@micah.riseup.net 1178949664 Q * marcfiu synthon.oftc.net charm.oftc.net 1178949664 Q * johnb synthon.oftc.net charm.oftc.net 1178949664 Q * micah synthon.oftc.net charm.oftc.net 1178949664 Q * djbclark synthon.oftc.net charm.oftc.net 1178949731 J * marcfiu ~mef@aegis.CS.Princeton.EDU 1178949731 J * djbclark dclark@opensysadmin.com 1178949731 J * johnb ~johnb@ge0.fw0.Athens.oh.us.splicednetworks.net 1178950893 Q * FireEgl Read error: Connection reset by peer 1178951769 J * FireEgl FireEgl@4.0.0.0.1.0.0.0.c.d.4.8.0.c.5.0.1.0.0.2.ip6.arpa 1178952942 J * dna ~naucki@116-206-dsl.kielnet.net 1178955182 J * cdrx ~legoater@cap31-3-82-227-199-249.fbx.proxad.net 1178956232 Q * dna Quit: Verlassend 1178956719 J * zLinux ~zLinux@88.213.63.82 1178957263 J * ktwilight ~ktwilight@91.211-66-87.adsl-static.isp.belgacom.be 1178957549 Q * ktwilight Read error: Connection reset by peer 1178957558 J * ktwilight ~ktwilight@228.212-66-87.adsl-static.isp.belgacom.be 1178957642 Q * ktwilight_ Ping timeout: 480 seconds 1178958578 J * ktwilight_ ~ktwilight@226.214-66-87.adsl-static.isp.belgacom.be 1178958962 Q * ktwilight Ping timeout: 480 seconds 1178959008 J * ktwilight ~ktwilight@128.207-66-87.adsl-static.isp.belgacom.be 1178959112 Q * ktwilight_ Ping timeout: 480 seconds 1178959875 J * DavidS david@chello062178045213.16.11.tuwien.teleweb.at 1178960541 J * Blissex ~Blissex@82-69-39-138.dsl.in-addr.zen.co.uk 1178960685 Q * nebuchadnezzar Remote host closed the connection 1178962497 Q * zLinux Remote host closed the connection 1178962988 J * zLinux ~zLinux@88.213.63.82 1178965250 J * duckx ~Duck@tox.dyndns.org 1178967317 J * Guy- ROuuUxLMYO@chardonnay.math.bme.hu 1178967824 J * bonbons ~bonbons@158.64.111.102 1178968239 J * ema ~ema@rtfm.galliera.it 1178969114 J * Piet hiddenserv@tor.noreply.org 1178970897 J * weaselTM weasel@asteria.debian.or.at 1178970899 Q * weaselTM 1178971862 J * pyquila gerbens@82.94.222.35 1178972337 Q * duckx Ping timeout: 480 seconds 1178972358 J * duckx ~Duck@tox.dyndns.org 1178973222 Q * duckx Ping timeout: 480 seconds 1178974437 J * duckx ~Duck@tox.dyndns.org 1178974476 J * pyquila_ gerbens@82.94.222.35 1178974483 J * daniel_hozac_ ~daniel@c-2f1472d5.08-230-73746f22.cust.bredbandsbolaget.se 1178974484 J * click_ click@ti511110a080-0476.bb.online.no 1178974493 J * ema_ ~ema@rtfm.galliera.it 1178974500 J * Adrinael_ adrinael@rid7.kyla.fi 1178974501 J * harry_ ~harry@d54C2508C.access.telenet.be 1178974509 J * kaner_ kaner@strace.org 1178974510 J * n01101111x ~nox@static.88-198-17-175.clients.your-server.de 1178974511 J * bon^ ~bon@stfu.rtfm.cz 1178974517 Q * cdrx Quit: Leaving 1178974528 Q * pyquila charon.oftc.net neutron.oftc.net 1178974528 Q * ema charon.oftc.net neutron.oftc.net 1178974528 Q * nox charon.oftc.net neutron.oftc.net 1178974528 Q * click charon.oftc.net neutron.oftc.net 1178974528 Q * daniel_hozac charon.oftc.net neutron.oftc.net 1178974528 Q * kaner charon.oftc.net neutron.oftc.net 1178974528 Q * nou charon.oftc.net neutron.oftc.net 1178974528 Q * Adrinael charon.oftc.net neutron.oftc.net 1178974528 Q * bon charon.oftc.net neutron.oftc.net 1178974528 Q * harry charon.oftc.net neutron.oftc.net 1178974528 N * n01101111x nox 1178974645 Q * Piet Ping timeout: 480 seconds 1178974650 Q * weasel Ping timeout: 480 seconds 1178974709 N * ema_ ema 1178974995 Q * duckx Ping timeout: 480 seconds 1178975050 J * duckx ~Duck@tox.dyndns.org 1178975515 N * Bertl_zZ Bertl 1178975526 M * Bertl morning folks! 1178975558 N * daniel_hozac_ daniel_hozac 1178975561 M * daniel_hozac morning Bertl! 1178975682 Q * duckx Ping timeout: 480 seconds 1178975873 N * Adrinael_ Adrinael 1178976026 Q * ema Quit: leaving 1178976200 J * duckx ~Duck@tox.dyndns.org 1178979539 M * Guy- hi 1178979594 M * Guy- daniel_hozac: low priority wishlist item for util-vserver: vserver-stat should have a switch that causes it to report memory requirements in bytes, not megabytes and times in seconds only (would be useful for graphing) 1178979626 M * daniel_hozac why don't you just use the APIs? 1178979626 M * Bertl Guy-: you don't want to 'graph' from vserver-stat 1178979654 M * Guy- Bertl: why is that? 1178979658 M * Bertl Guy-: more precisely, you do not even want to graph from procfs :) 1178979658 M * daniel_hozac Bertl: it should be fine with 0.30.213, that uses the rlimit_stat. 1178979673 M * Guy- daniel_hozac: because that involves writing code :) 1178979692 M * daniel_hozac parsing out the values isn't "writing code"? 1178979728 M * Guy- it's not the same as writing a C program that calls a kernel API, no 1178979817 M * daniel_hozac Python should be fine too. 1178979831 M * Guy- I imagine I may not be the only one who'd like to draw munin graphs that show vserver memory and cpu usage, so this functionality would, I think, be useful to a wider audience 1178979843 M * daniel_hozac you could even use vcmd. 1178979854 M * Guy- vcmd? 1178979870 M * daniel_hozac Bertl: why wouldn't you want to graph from procfs? 1178979876 M * daniel_hozac http://vserver.13thfloor.at/Experimental/TOOLS/vcmd-0.08.tar.bz2 1178979922 M * Bertl daniel_hozac: because procfs will lock the kernel and requires the cpus to sync (in certain cases) 1178979934 M * Bertl daniel_hozac: besides that, the procfs is a very slow and poor interface 1178979953 M * daniel_hozac right, okay. 1178979981 M * Bertl starting vserver-stat over and over again (same goes for vmcd) is also a poor choice for graphing 1178980016 M * Guy- Bertl: uh, the word 'privileges' contains no d :) (just looking at vcmd.c) 1178980033 M * Bertl the best (and least intrusive) way IMHO would be a small code fragment in something like rrdcollect ... 1178980051 M * Bertl Guy-: ah, tx, will fix in the next release ... (patches are welcome) 1178980090 M * Guy- Bertl: would you like this typo fix as a diff? 1178980110 M * Bertl that would be nice, maybe check for other typos too :) 1178980166 M * Guy- and calling vserver-stat or vcmd once every five minutes is really such a bad idea? 1178980409 M * Bertl no, every five minutes is fine 1178980420 M * Bertl but that won't give you nice graphs :) 1178980695 M * Guy- I'm mostly interested in long-term trends 1178980744 M * Guy- maybe I can average the last 5 readings (or, in the case of time, derive first and take average afterwards) 1178980773 M * Guy- anyway, I have a diff with my spelling/style changes for vcmd.c; where would you like it? mail? dcc? 1178980800 M * Bertl I would suggest leaving this kind of calculations to something like rrd .. for the diff, just send it to me or upload it somewhere where I can reach it 1178980903 M * Guy- sure, I'd use rrd to do them 1178980907 M * Guy- with CDEFs 1178980922 M * Guy- herbert@13thfloor? 1178980929 M * Bertl yep, tx 1178980961 M * mEDI_S Guy-: http://collectd.org/plugins/vserver.shtml 1178981094 M * Bertl mEDI_S: does that use the API or proc? 1178981110 M * mEDI_S proc 1178981168 M * Guy- once every 10 seconds...? 1178981199 M * Guy- but I'll take a look at it, thanks 1178981255 M * Bertl you can adjust the frequency of collectd 1178981289 J * weasel weasel@2001:858:10f:6::1 1178981294 J * nou Chaton@causse.larzac.fr.eu.org 1178981323 M * Bertl wb weasel! nou! 1178981345 J * SoftIce ~bongo@vc-196-207-45-253.3g.vodacom.co.za 1178981358 M * SoftIce hi, how does 1 sugest the best way to build a vserver within debian 1178981362 M * SoftIce using debootstrap ? 1178981379 M * Bertl vserver - build --help 1178981397 M * SoftIce so you don't sugest I use deboostrap script /path/to/vserver? 1178981412 M * daniel_hozac no. 1178981426 M * daniel_hozac why would you, when util-vserver can do that for you? 1178981454 M * Guy- SoftIce: I used vserver foo build -m debootstrap --context 18 --hostname mail.foo.de --netdev eth0 --netbcast 172.18.255.255 --netprefix 16 --interface foo=eth0:172.18.16.4/16 --flags persistent --initstyle plain -- -d etch -m http://ftp2.de.debian.org/debian -s /usr/lib/debootstrap/scripts/etch -- --arch i386 1178981460 M * SoftIce ok, so rather the normall way I use it, newvserver-vars ? DIST=.... && newvserver -v ? 1178981515 M * Bertl forget newvserver it is just complicating things 1178981520 M * daniel_hozac Guy-: why the -s? 1178981579 M * Guy- daniel_hozac: I got into the habit of using it when I had a custom 'distribution', so now I specify it without thinking 1178981603 M * Guy- daniel_hozac: I was wondering about netbcast and netprefix though; aren't those redundant with --interface? 1178981613 M * daniel_hozac yes. 1178981614 M * SoftIce Bertl: complicates in what sense? 1178981624 M * daniel_hozac Guy-: as is --netdev. 1178981629 M * Guy- right 1178981637 M * daniel_hozac SoftIce: in that it serves no real purpose. 1178981666 M * Bertl SoftIce: in several ways: first, it breaks the section separation vserver - build does, second you ahve to remember different syntaxes now, third it cannot build non debian guests 1178981698 M * SoftIce I see, thank you 1178981732 M * SoftIce I feel that some of the sections of the wiki should be removed then, and have a standard way 1178981802 M * Guy- I'd agree that the wiki needs to be reorganized because it's a bit chaotic now; however, I think those who could do it because they know enough about it are busy writing code :) 1178981883 M * Bertl (or at least don't want to write wiki pages :) 1178981941 M * SoftIce heh 1178982230 M * SoftIce do you have to specify an CIDR range if you just using ip 1178982999 J * ramon ~ramon@116.Red-88-5-228.staticIP.rima-tde.net 1178983004 M * SoftIce http://paste.linux-vserver.org/1762 1178983008 M * ramon Hi. 1178983008 M * SoftIce do I just ignore this? 1178983043 M * daniel_hozac SoftIce: did you at all read what me and Bertl said? 1178983093 M * SoftIce yes 1178983133 M * SoftIce well do you mind telling me what 'wiki' article to read 1178983141 M * SoftIce as debian/ubuntu/fedora, etc 1178983145 M * SoftIce can't be used in my case 1178983210 Q * ramon 1178983236 M * daniel_hozac none. 1178983243 M * daniel_hozac just use vserver ... build. 1178983330 M * Guy- SoftIce: use the command line like the one I used, and perhaps specify the debootstrap script for feisty 1178983550 M * SoftIce vserver blackhole build -m debootstrap --hostname=blackhole.inet-corp.com --interface eth0:65.111.177.75/24 -- -d feisty -m http://us.archive.ubuntu.com/ubuntu 1178983786 J * hardwire ~bip@rdbck-3402.palmer.mtaonline.net 1178984023 M * SoftIce daniel_hozac: you wouldn't have a link by any chance to documentation about setting up locales? everytime I build a vserver i get locale issues for ever :) 1178984054 M * daniel_hozac dpkg-reconfigure locales? 1178984128 M * SoftIce http://paste.linux-vserver.org/1764 1178984178 M * Guy- apt-get install locales? 1178984189 M * Guy- or unset LANG 1178984240 M * SoftIce unset lang works ;) 1178984291 M * Bertl okay, translocating now ... back later ... 1178984296 N * Bertl Bertl_oO 1178984347 M * Guy- SoftIce: you might also do echo en_US.UTF-8 UTF-8 >>/var/lib/locales/supported.d/local; locale-gen 1178984376 M * SoftIce Guy-: I'm from south africa 1178984381 M * SoftIce so would en_ZA.UTF work ? 1178984430 M * Guy- posibly; I was just guessing because your LANG was set to "en_US.UTF-8" 1178984438 M * Guy- I have no idea if there is an en_ZA locale 1178984519 M * SoftIce great, i'm adding this to my new vserver build documentation I can put on the wiki ! 1178984596 M * Guy- I think it's ubuntu specific (might also apply to sid though); earlier debian used /etc/locale.gen instead of /var/lib/locales/supported.d/ 1178984676 M * SoftIce ahh 1178984694 M * SoftIce anyone here use control panels for client hosting, wondering what 1 would sugest is best that is free 1178984696 M * SoftIce root@blackhole:/# echo en_US.UTF-8 UTF-8 >>/var/lib/locales/supported.d/local 1178984698 M * SoftIce root@blackhole:/# locale-gen 1178984698 M * SoftIce Generating locales... 1178984698 M * SoftIce en_US.UTF-8... done 1178984698 M * SoftIce Generation complete. 1178984701 M * SoftIce errr sorry about that 1178984726 M * SoftIce webcp, ispconfig, webmin ? 1178984753 M * SoftIce I need something I can add quotas, etc, set b/w limitation per domain, show statistics 1178984754 M * SoftIce etc 1178985065 J * ramon ~ramon@116.Red-88-5-228.staticIP.rima-tde.net 1178985079 M * ramon Hello 1178985121 M * ramon Is it posible to have an IP address that is different in the host and in the VM? For instance, having 127.0.0.1 defined in a VM, as an address local to the machine. 1178985177 Q * SoftIce Read error: Connection reset by peer 1178988673 M * daniel_hozac ramon: 127.0.0.1 is remapped to the first IP address assigned to the guest 1178988710 M * ramon Interesting. 1178990007 M * ramon I see one issue. If my first IP address is a not local, an application listening on 127.0.0.1 will be listening on the outside network. 1178990108 M * DavidS ramon: you can change the order of interfaces by naming the directories in /etc/vservers/*/interfaces/ appropriatly 1178990121 M * ramon sure. 1178990121 M * DavidS ( ... as i learned the hard way ) 1178990150 M * ramon But it might be surprising if one has an app listening on 127.0.0.1 and believing that it is not accesible from outside. 1178990171 M * DavidS you can't have both 1178990184 M * DavidS and you can make appropriate iptables on the host 1178990388 M * ramon It is not an issue of functionality. One can declare an interface 0 device lo addr 127.0.0.10 or whatever. The issue is surprise. 1178990451 M * ramon In general, I think that VServer is great software without documentation. Perhaps I will convince my boss to write some. I am not bad at it. 1178990474 M * Guy- that would be a great idea 1178990485 M * DavidS indeed :) 1178990788 M * daniel_hozac there's a reason the website's a wiki ;) 1178990822 M * sid3windr is there?! 1178990966 M * Guy- yes, it's so the developers can lean back and wait for the users to write the docs ;) 1178990998 M * DavidS ah .. that's why vserver is so cool and the docs are chaotic :) 1178991177 M * daniel_hozac yes, we have such lazy users :) 1178992634 J * pmenier ~pmenier@ACaen-152-1-51-110.w83-115.abo.wanadoo.fr 1178992646 M * ramon Can I disable 127.0.0.1 binding to some interface? I want the virtual machine to be able to connect to host's 127.0.0.1, but not to listen to it, or o see what ports are available on it. 1178992654 M * pmenier Hello 1178992668 M * ramon Because I have a MySQL instance running on 127.0.0.1 1178992675 M * daniel_hozac sure, just remove that part of the kernel. 1178992682 M * daniel_hozac +patch 1178992684 M * ramon :-) 1178992697 M * ramon I would prefer a configuration option. 1178992705 M * daniel_hozac there isn't one. 1178992719 M * daniel_hozac (well, there is in 2.3) 1178992780 M * ramon Good. 1178992787 M * ramon Making 127.0.0.1 somehow special is ugly. 1178992818 M * daniel_hozac and you think it would be better to just fail since that address is not available inside the guest? 1178992869 M * ramon The current behaviour is an excellent default. 1178992897 M * ramon It just must be posible to connect to a service on the host running on 127.0.0.1 1178992908 M * ramon Without making the interface available to the VM. 1178992914 M * Guy- daniel_hozac: can I have filesystems the guests mount from their fstab fsck'd? does vserver start do anything like this? 1178992958 M * Guy- ramon: OTOH, if you think of guests as separate systems, they shouldn't be able to reach the hosts's 127.0.0.1 either 1178992970 M * Guy- ramon: so this might also violate the principle of least surprise 1178993006 M * ramon One of the advantadges of VServer is that it enables one a deeper degree of integration. 1178993021 M * Guy- or isolation ;) 1178993027 M * ramon Guy: as said, the current behaviour is an excellent default. It just should not be enforced. 1178993083 M * ramon It should be posible to connect to something on 127.0.0.1 if one wishes. In this way, I can make a service available to hosts and to VMs. 1178993096 M * Guy- yes, that'd be nice 1178993198 M * pmenier I've posted a bug : paste.linux-verser.org/1769 . It happens after few days running fine on kernel-2.6.21 1178993243 M * daniel_hozac Guy-: no, it doesn't, at least not yet. 1178993265 M * Guy- ok, thanks 1178993309 M * daniel_hozac ramon: and why can't you just use the host's IP address for that? 1178993315 M * daniel_hozac ramon: or even UNIX sockets? 1178993372 M * daniel_hozac pmenier: very interesting... 1178993389 M * ramon Because it is a Java application. 1178993409 M * daniel_hozac so? 1178993418 M * ramon Java applications cannot talk to Unix sockets. 1178993424 M * daniel_hozac really? 1178993428 M * ramon Yes, really. 1178993434 M * ramon Only TCP/IP. 1178993438 M * daniel_hozac that's... sad. 1178993447 M * daniel_hozac but still, the host's IP address should be fine then, no? 1178993453 M * ramon I hope that now that Java is GPL these nuisances can be fixed. 1178993505 M * ramon If I were daniel_hozac I would say, just download the JDK sources and patch them to add support of Unix sockets :-) 1178993530 M * daniel_hozac well, i'd say, is that also true for gcj? 1178993573 M * pmenier daniel_hozac: it sounds like problem about tty_devnum as it appeared on 2.6.20 ... 1178993580 M * daniel_hozac pmenier: yep. 1178993593 M * ramon I don't know, but gcj is not stable enough. 1178993787 M * ramon daniel_hozac: about the host's IP address, because I don't want to make the MySQL avaible to the outside, only the VMs. 1178993795 J * pmenier1 ~pmenier@ACaen-152-1-96-175.w83-115.abo.wanadoo.fr 1178993798 M * daniel_hozac that's what iptables is for? 1178993831 M * Guy- ramon: how about having it listen on 127.33.06.1? 1178993834 M * ramon Well, that could be a solution. 1178993862 M * ramon Guy: that would be other, but it could confuse other apps using MySQL. 1178993877 M * Guy- not if you listen on _both_ addresses 1178993906 M * ramon I have been googling for how to make MySQL bind to several addresses, without success. 1178993936 M * Guy- ah, that could be a problem then 1178993956 M * Guy- run a separate mysql for the vservers and set up a replicating cluster ;) 1178993960 M * ramon Is that posible? I think that bind(2) accepts one address as argument only. 1178993962 M * ramon :-) 1178993972 M * daniel_hozac run it in a chbind? 1178994000 M * Guy- daniel_hozac: can chbind cause 0.0.0.0 to mean 127.0.0.1 and 127.33.06.1? 1178994009 M * daniel_hozac yes. 1178994031 M * Guy- OK, there you are then 1178994049 M * Guy- it's a ... workaround 1178994060 Q * pmenier Ping timeout: 480 seconds 1178994068 M * daniel_hozac i'd say hack. 1178994076 Q * pmenier1 Quit: Leaving 1178994085 M * Guy- now now, there's no call for name-calling :) 1178994125 J * pmenier ~pmenier@ACaen-152-1-96-175.w83-115.abo.wanadoo.fr 1178994126 M * ramon What I am going to do is to setup mysql to listen to 127.0.0.2, because VServer does nothing special with it. 1178994139 M * ramon It may cause some confusion, but it is acceptable. 1178994286 M * ramon Other solution would be to setup some kind of redirection of connections to 127.0.0.2 to 127.0.0.1 1178994302 M * Guy- you'd have to do that with nat 1178994325 M * daniel_hozac in which case it's easier to just make it listen on the host's IP address and deny any non -i lo access to it. 1178994325 M * Guy- with rinetd you lose the ability to look at the source address 1178994355 M * Guy- daniel_hozac: that's not fail-safe in the sense that if the firewall rules aren't loaded or are messed up, your mysql is wide open 1178994430 M * daniel_hozac same is true for the NAT-rule. 1178994518 M * Guy- no 1178994536 M * Guy- if you're DNATing 127.0.0.2 to 127.0.0.1 1178994545 M * Guy- and the rule isn't loaded for some reason 1178994554 M * Guy- you may not be able to connect to mysql 1178994558 M * Guy- but no one else can either 1178994561 M * Guy- so it's fail-safe 1178994575 M * daniel_hozac i was more referring to the messed up case. 1178994604 M * Guy- with 'messed up' I meant something like 'wrong order' 1178994604 Q * Johnnie Read error: Connection reset by peer 1178994628 M * Guy- not that you mess up the specific rule 1178994633 J * Johnnie ~jdlewis@c-67-163-247-109.hsd1.pa.comcast.net 1178994863 M * ramon nat would be too complicated. 1178995511 M * pmenier . 1178995943 M * Guy- wow. I have a running vserver that vserver-stat doesn't see. 1178995949 M * Guy- I can enter it and everything 1178995960 J * nebuchadnezzar ~nebu@zion.asgardr.info 1178996621 M * Guy- http://paste.linux-vserver.org/1772 1178996639 M * Guy- it's a persistent context; if I run a process in it, it becomes visible to vserver-stat as well 1178997161 M * daniel_hozac Guy-: upgrade to util-vserver 0.30.213. 1178997189 M * daniel_hozac vserver-stat isn't full of lies anymore. 1178997201 M * Guy- I did. 1178997222 M * daniel_hozac then your kernel is too old. 1178997227 M * Guy- that's a possibility, yes 1178997282 N * Bertl_oO Bertl 1178997289 M * Bertl back now ... 1178997331 M * daniel_hozac Bertl: check out http://paste.linux-vserver.org/1769 1178997422 M * Bertl ah nice, probably a bug in my port? 1178997439 M * daniel_hozac or the bug from hell is back! ;) 1178997462 M * pmenier Hi Bertl ! Sorry but as you say the hell is back :-) 1178997519 M * Bertl well, as we didn't see it with 2.6.19/20 anymore, I assume it is either a bug in the .21 port or a mainline issue (unlikely) 1178997852 J * bzed ~bzed@dslb-084-059-126-057.pools.arcor-ip.net 1178998952 M * Bertl welcome bzed! 1178998960 M * bzed thanks Bertl 1178998978 M * daniel_hozac Bertl: yeah, it looks like the vx_check is still in include/linux/pid.h:do_each_pid_task. 1178999091 J * mjt ~mjt@nat.corpit.ru 1178999107 M * Bertl welcome mjt! 1178999118 M * mjt wow! Hello! 1178999145 M * daniel_hozac pmenier: i think http://people.linux-vserver.org/~dhozac/p/k/delta-pid_task-fix01.diff should fix it. 1178999155 M * daniel_hozac pmenier: (that patch will give you offsets, but it should apply) 1178999174 M * pmenier ok i try it now 1178999204 M * pmenier i just apply it to my cuurent kernel-tree ? 1178999216 M * daniel_hozac yep. 1178999304 M * pmenier Hunk #1 succeeded at 111 (offset -14 lines 1178999315 M * daniel_hozac exactly. 1178999328 M * pmenier ok. I compil now 1178999693 M * transacid i think there is something broken with my machine http://paste.linux-vserver.org/1775 1178999727 M * Bertl transacid: nope, same issue 1178999761 M * daniel_hozac just on a much older kernel :) 1178999766 M * transacid Bertl: what do you mean? 1178999779 M * daniel_hozac transacid: upgrade to 2.2.0 and you'll see it has been fixed... 1178999790 M * transacid daniel_hozac: ok 1178999874 M * Bertl daniel_hozac: hmm ... I wonder why it isn't in my sources though ... 1178999890 M * daniel_hozac Bertl: the vx_check? 1178999893 M * transacid daniel_hozac: for 2.6.20.22 or 2.6.21? 1178999902 M * Bertl daniel_hozac: the patch, yes 1178999917 M * daniel_hozac transacid: 2.6.21-vs2.2.0-rc1 has the same problem. 1178999926 M * transacid ok 1178999928 M * daniel_hozac transacid: 2.6.20.11 or 2.6.19.7 would be wiser choices. 1178999943 M * transacid 2.6.20.11 then 1178999963 M * Bertl I'd assume the 2.2.0 patch for 2.6.20.11 is missing that too 1178999977 M * daniel_hozac IIRC it wasn't as critical in 2.6.20. 1178999989 M * daniel_hozac do_each_task_pid was used for the tty checks. 1179000083 M * daniel_hozac do_each_pid_task is only used in 3 places (in 2.6.20), all of which are in signal related places. 1179000496 M * Bertl okay, why is it 'now' critical with 2.6.21? 1179000516 M * daniel_hozac do_each_task_pid doesn't exist anymore, seems like they've all been converted to do_each_pid_task. 1179000540 M * Bertl ah, k, so it won't hurt for 2.6.20 but it hurts with 2.6.21 1179000562 M * daniel_hozac exactly. 1179000579 M * Bertl so should we apply the patch for 2.6.20 in the future? 1179000657 M * daniel_hozac well, i think so, but it really only strikes for SIGIO/SIGURG (and maybe __kill_pgrp_info in some case i can't quite come up with right now). 1179000983 M * pmenier i've finished and reboot 1179001001 M * pmenier all seems ok 1179001208 Q * bon^ Quit: Lost terminal 1179001475 M * pmenier do you know why this bug always appears in a random way ? 1179002076 Q * Blissex Quit: Goodbye... 1179002084 J * Blissex ~Blissex@82-69-39-138.dsl.in-addr.zen.co.uk 1179002105 M * daniel_hozac that's just the nature of it. 1179002147 M * daniel_hozac it's a weird bug, went unnoticed for weeks. 1179003092 M * pmenier so i am not a lucky guy ;) 1179003535 Q * ruskie Ping timeout: 480 seconds 1179004149 Q * Hollow Quit: Disconnecting from stoned server. 1179004161 J * Hollow ~hollow@styx.xnull.de 1179004574 M * mjt is `vuname context' attribute settable from within a guest, like usual uname() fields? 1179004596 M * Bertl nope 1179004607 M * mjt yay good! :) 1179004617 M * Bertl :) 1179004800 Q * meandtheshel1 Quit: Leaving. 1179005004 J * meandtheshell ~markus@85-124-36-228.dynamic.xdsl-line.inode.at 1179005004 Q * FireEgl Read error: Connection reset by peer 1179005242 J * ruskie ruskie@ruskie.user.oftc.net 1179005560 Q * Blissex Remote host closed the connection 1179005957 J * FireEgl FireEgl@Sebastian.Atlantica.US.TO 1179007620 Q * FireEgl Ping timeout: 480 seconds 1179007926 Q * ruskie Read error: Connection reset by peer 1179008201 J * FireEgl FireEgl@FireEgl.CJB.Net 1179008331 J * ruskie ruskie@ruskie.user.oftc.net 1179008367 Q * FireEgl Read error: Connection reset by peer 1179009097 Q * meandtheshell Quit: Leaving. 1179009116 J * meandtheshell ~markus@85-124-36-228.dynamic.xdsl-line.inode.at 1179009233 J * ktwilight_ ~ktwilight@149.111-66-87.adsl-dyn.isp.belgacom.be 1179009250 Q * ruskie Read error: Connection reset by peer 1179009426 J * ruskie ruskie@ruskie.user.oftc.net 1179009521 Q * ktwilight Ping timeout: 480 seconds 1179009923 Q * bonbons Quit: Leaving 1179010248 Q * tanjix Ping timeout: 480 seconds 1179010762 Q * meandtheshell Quit: Leaving. 1179010825 J * meandtheshel1 ~markus@85-124-36-228.dynamic.xdsl-line.inode.at 1179011488 Q * ramon Quit: Leaving 1179011984 J * edog ~edog@office.aichyna.com 1179012263 J * dreamind apwdsl@p548A8346.dip0.t-ipconnect.de 1179012294 N * dreamind Guest126 1179012775 J * ktwilight ~ktwilight@215.80-66-87.adsl-dyn.isp.belgacom.be 1179013129 Q * ktwilight_ Ping timeout: 480 seconds 1179013133 J * ktwilight_ ~ktwilight@194.70-66-87.adsl-dyn.isp.belgacom.be 1179013277 Q * ktwilight Ping timeout: 480 seconds