1323734427 Q * dowdle Remote host closed the connection 1323741321 Q * nicholi Quit: leaving 1323742784 N * ensc Guest20209 1323742793 J * ensc ~irc-ensc@p4FEC7852.dip.t-dialin.net 1323743068 Q * yang Remote host closed the connection 1323743076 J * yang yang@boneym.linuxshell.org 1323743109 N * yang Guest20210 1323743203 Q * Guest20209 Ping timeout: 480 seconds 1323746678 M * Bertl off to bed now .. have a good one everyone! 1323746684 N * Bertl Bertl_zZ 1323749000 Q * FireEgl Quit: Leaving... 1323752906 Q * ex Ping timeout: 480 seconds 1323754003 Q * neofutur Quit: leaving 1323756515 J * ex ex@valis.net.pl 1323760245 J * ghislain ~AQUEOS@adsl2.aqueos.com 1323760352 J * ncopa ~ncopa@3.203.202.84.customer.cdi.no 1323760524 J * neofutur ~neofutur@sd-30672.dedibox.fr 1323762074 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1323763748 J * aj__ ~aj@87.253.171.198 1323766961 J * gucki ~gucki@80-218-125-247.dclient.hispeed.ch 1323770508 J * BenG ~bengreen@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com 1323773006 Q * BenG Quit: I Leave 1323774711 N * Bertl_zZ Bertl 1323774716 M * Bertl morning folks! 1323774971 J * BenG ~bengreen@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com 1323775688 M * Bertl off for now ... bbl 1323775694 N * Bertl Bertl_oO 1323776926 Q * mnemoc Quit: Lost terminal 1323776958 J * mnemoc ~amery@shell.opensde.net 1323777073 M * gucki hey there 1323777463 M * gucki it seems naddress --remove --nid 10001 --ip 192.168.0.123/24 does not work, but ip addr del 192.168.0.123/24 dev eth0 works anyway. Is it okay to simply skip the naddress call or does it leak resources or cause any other troubles? 1323777670 M * daniel_hozac naddress --remove is not implemented. 1323777692 M * daniel_hozac if you don't run it, the guest will still be able to use it, if you add the address back. 1323777710 M * daniel_hozac in order to remove the address, you'll have to run --set with the IP addresses you wish to use. 1323778000 M * gucki daniel_hozac: you mean naddress --set --nid 10002 --ip 192.168.0.123/24 to change from 10001 to 10002? 1323778029 M * gucki daniel_hozac: I can simply to both, --add and then again --set (so I don't care if it's the first assignment or not) 1323778146 M * gucki daniel_hozac: btw, did you read about the vserver-util bug from yesterday (exit code 255) and my github proposal? :) 1323778976 M * Bertl_oO you want to move the IP from one guest to the other? 1323779136 M * gucki Bertl_oO: sometimes, but sometimes only remove it completely or to a different machine. I'd prefer to always remove it completely, and if I need it on antoher guest, I'll just add it there agin (using ip addr add followed by naddress..) 1323779235 M * Bertl_oO but without restarting the guest where you 'remove' the IP? 1323779393 M * gucki Bertl_oO: sorry, i dont really understand. when adding an ip, i first add it to the host and then add/assign it to the guest/ context. when removing, i remove/unassign it from the guest/ context (which does not work) and then remove it from the host. there's no need to restart the guest? 1323779455 M * gucki Bertl_oO: my usage case is for example apache running inside the guest and using severals ips for ssl. now when a virtal host with ssl goes away, i'd like to remove the ip from the guest without having to restart. 1323779479 M * gucki a few days later i might want to reuse the same ip on antoher machine, guest or the same...but i dont' know upfront. 1323780509 M * Bertl_oO well, you need to 'set' all other IPs (except the one you want to remove) for now 1323781397 M * daniel_hozac gucki: the bug is already fixed. 1323781414 M * daniel_hozac as for github, we already have everything github provides, without the github annoyances. 1323782038 M * gucki daniel_hozac: great thanks :). what annoys you with github? i really like pull requests, issue tracker, etc.. 1323782067 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647 1323782096 Q * Aiken Remote host closed the connection 1323782119 M * daniel_hozac there already is an issue tracker. 1323782155 M * daniel_hozac and if you want to do a pull request, just list it in the bug report... 1323782475 M * gucki daniel_hozac: mh, i cant find it in the docs http://linux-vserver.org/util-vserver:Cheatsheet. one of the best things about github is having one account for all projects. no need to signup here and there, just to file a bug report or make a quick bug fix 1323782543 M * gucki Bertl_oO: sorry, now I'm even more confused. why do I have to do a set on all other ips of the guest (which i dont want to change at all)? 1323782608 M * daniel_hozac because set removes all the current IPs and adds back the ones specified. 1323782667 M * daniel_hozac https://savannah.nongnu.org/projects/util-vserver/ is the util-vserver project website. 1323782697 M * gucki daniel_hozac: ah ok. so basically i never need to use add/ remove, only using set should be enough, right? 1323782708 M * daniel_hozac sure. 1323782798 M * gucki daniel_hozac: great, thanks :) 1323782813 M * gucki daniel_hozac: so linux vserver isn't using git but svn? 1323782888 M * daniel_hozac util-vservre is in git. 1323782923 M * daniel_hozac linux-vserver doesn't use any conventional named system. 1323791624 J * dowdle ~dowdle@scott.coe.montana.edu 1323792324 Q * ncopa Quit: Leaving 1323796357 J * bonbons ~bonbons@2001:960:7ab:0:8156:52f1:3529:f8ec 1323796554 Q * aj__ Ping timeout: 480 seconds 1323797348 Q * BenG Quit: I Leave 1323798885 N * Bertl_oO Bertl 1323798889 M * Bertl back now ... 1323799501 Q * gucki Remote host closed the connection 1323799684 J * Guest20303 ~digital@109.195.195.9 1323799862 P * Guest20303 1323800842 J * nicholi ~nicholi@rrcs-76-79-196-34.west.biz.rr.com 1323800911 M * Bertl off for a nap ... bbl 1323800918 N * Bertl Bertl_zZ 1323806614 J * FireEgl FireEgl@2001:470:e056:1:d59b:dc63:b7be:65d7 1323807798 Q * puck Quit: Coyote finally caught me 1323809589 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f 1323809733 N * Bertl_zZ Bertl 1323809736 M * Bertl back now ... 1323811349 Q * arekm Quit: leaving 1323811780 J * arekm ~arekm@ixion.pld-linux.org 1323813892 Q * bonbons Quit: Leaving 1323816917 Q * ghislain Quit: Leaving. 1323817465 N * ensc Guest20323 1323817474 J * ensc ~irc-ensc@p4FEC5D69.dip.t-dialin.net 1323817585 Q * Guest20323 Ping timeout: 480 seconds 1323818396 J * bastiaan ~bastiaan@sh.welmers.net 1323818417 M * bastiaan hi 1323818429 M * bastiaan someone experience with the vserver kernel in debian squeeze? 1323818469 M * bastiaan it seems the virtual loopback interface is missing, although the kernel config parameter is present 1323818486 M * Bertl there is a lot of stuff missing in debian kernels 1323818548 M * bastiaan yes, for now I had to maintain my own kernel, I did hope it would not be neccessary with squeeze, but false hope... 1323818970 M * Bertl debian has a history of picking broken kernels and incomplete patches 1323819000 M * Bertl but once they picked them, they stick to them like glue 1323819044 M * bzed reporting enough bugs should help. and not letting waldi just close them without any other action 1323819064 M * bzed otherwise nobody will notice 1323819089 M * Bertl well, IIRC, the problem is that most 'bugs' are classified as 'features' and do not really get fixed 1323819098 M * Bertl only 'security issues' get fixed 1323819141 M * bzed also: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574529 1323819191 M * bzed Bertl: thats not true. but it means that you have to convince a kernel developer that the bug needs to be fixed in stable (including a proper explanation, and yes, no new features) 1323819199 M * bzed so he'll fix it 1323819225 M * bzed and is able to convince the release team then, which is not that hard 1323819235 M * bzed would be easier if vserver would be in the kernel 1323819274 M * Bertl see, there is the point, _I_am_ the upstream authority on the Linux-VServer kernel 1323819309 M * Bertl so, when I say, this or that needs to be fixed, that's like somebody fixing it in mainline 1323819324 M * bzed from a distribution POV, you are upstream of yet another kernel patch 1323819346 M * Bertl nevertheless, debian doesn't fix such things, they just make workarounds and lengthy discussions with no outcome 1323819350 M * bzed even if you say it needs to be fixed, you still need to convince a debian developer that you are right 1323819372 M * Bertl so, my advice for debian users: build your own kernel, avoid all the issues 1323819377 M * bzed which is usually an issue with some person of the debian kernel team which handles vserve runfortunately 1323819481 M * bzed the kernel team became much better to work with during the last few years, at least most of them 1323819483 M * Bertl personally I do not see an advantage in having a debian Linux-VServer kernel at all 1323819502 M * bzed well, there are beginenrs which would like to play around 1323819523 M * Bertl they can download the benq package for example 1323819528 M * bzed its an easy way for them to test varous distributions/whatever without having to build a kernel and understand it 1323819587 M * bzed unfortunately I have to say that these days its just easier to run virtualbox or virt-manager with kvm than building a kernel on your own 1323819590 M * Bertl *beng sorry 1323819619 M * bastiaan unfortunaltly I have been struggeling a lot with other problems in squeeze, getting sick of it 1323819630 M * bzed and if you are a beginner, you probably don't know where to search, and looking into your package manager provides easy choices 1323819647 M * Bertl I agree, but what is the point in installing a debian Linux-VServer kernel, when you ahve to replace it to actually use it? 1323819665 M * Bertl it only gives the impression that Linux-VServer is not properly working 1323819732 M * Bertl but don't get me wrong, I'm fine with debian packaging (or not packaging) whatever kernel they like ... 1323819783 M * bzed well, where are according bugs in the debian bug tracker? on the first look I couldn't find a single vserver related one (which might be due to the BTS failing on the large number of kernel bugs...) 1323819785 M * bastiaan well, rpm has the advantage you can run 32 and 64 packages, deb has not 1323819793 M * bastiaan +bits 1323819835 M * bzed you mean you can install 32bit packages on a 64bit platform? 1323819850 M * bzed that will be fixed with the next release, multiarch is coming 1323819854 M * bastiaan yes 1323819870 M * bastiaan well, fine, by the time it's almost not neccessary anymore :) 1323819890 M * Bertl not sure how that is Linux-VServer related though :) 1323819896 M * bastiaan so they finaly use a /lib and /lib64 instead of a /lib32 and /lib? :) 1323819898 M * bzed me neither :) 1323819928 M * bzed Bertl: but back to bugs: if you have sombody complaining about issues in squeeze, please poke them to use reportbug to report a bug against linux-2.6 1323820057 M * Bertl feel free to do so, roughly once every week somebody comes here asking for support with a debian Linux-VServer kernel 1323820088 M * Bertl my usual advice is to build a new one or update to the beng packages, which usually solves the issues 1323820135 M * Bertl that's quick and easy and last but not least effective for the end user and myself ... 1323820281 M * bastiaan beng packages? 1323820346 M * bzed Bertl: I'm rarely reading here. but if you complain about broken kernels, please ask users to report bugs. otherewise they won't be fixed for sure 1323820421 M * bastiaan I'll do tomorrow 1323820421 M * bastiaan :) 1323820469 M * Bertl bzed: I alway hint to debian users to complain to debian 1323820489 M * Bertl but AFAIK, it never did actually help or improve issues 1323820528 M * bzed if people have a debian bug number, I can try to prod them 1323820537 M * bzed well, not the people but the kernel develoeprs 1323820542 M * Bertl http://repo.psand.net/info/ 1323820544 M * bzed but not without a properly reported bug