1221955290 J * ikorvine ~ikorvine@anonymous.vaninollc.com 1221955316 M * ikorvine hey can someone lend me a hand, how can I create /dev/initctl for use with a djbdns vserver 1221955663 Q * almak Remote host closed the connection 1221955684 J * almak ~almak@proxy-sjc-1.cisco.com 1221956325 M * Bertl ikorvine: hmm, isn't that supposed to be created by init? 1221956531 M * ikorvine Bertl: quite possibly, init is running tho 1221956537 M * ikorvine and there is no initctl in /dev 1221956574 M * Bertl well, you can 'copy' it from the host, but it is a pipe 1221956592 M * ikorvine ah hmm 1221956592 M * Bertl i.e. if nothing is connected to it, it won't help you much 1221956597 M * ikorvine yea 1221958057 Q * esa Ping timeout: 480 seconds 1221958715 J * docelic ~docelic@78.134.207.60 1221959589 Q * laptopnenolod- Quit: this sh scripting is the language of the future 1221959614 J * laptopnenolod ~nenolod@pool-70-105-239-185.port.east.verizon.net 1221961044 M * Bertl ~okay, off to bed now .. have a good one everyone! 1221961052 N * Bertl Bertl_zZ 1221961555 Q * docelic Quit: http://www.spinlocksolutions.com/ 1221964847 J * derjohn_foo ~aj@p5B23E823.dip.t-dialin.net 1221965279 Q * derjohn_mob Ping timeout: 480 seconds 1221965675 Q * Aiken Remote host closed the connection 1221966685 J * esa bip@62.123.8.12 1221967231 J * Aiken ~Aiken@ppp118-208-28-181.lns2.bne1.internode.on.net 1221971766 J * laptopnenolod- ~nenolod@pool-70-105-239-185.port.east.verizon.net 1221972143 Q * laptopnenolod Ping timeout: 480 seconds 1221973841 Q * hparker Quit: Read error: 104 (Peer reset by connection) 1221973906 J * hparker ~hparker@linux.homershut.net 1221975114 Q * pmenier Ping timeout: 480 seconds 1221975129 J * pmenier ~pmenier@ACaen-152-1-30-244.w83-115.abo.wanadoo.fr 1221976107 Q * hparker Remote host closed the connection 1221976805 Q * almak Remote host closed the connection 1221976828 J * almak ~almak@proxy-sjc-1.cisco.com 1221977529 J * ntrs ~ntrs@77.29.71.34 1221978125 J * friendly ~friendly@ppp59-167-79-93.lns1.mel6.internode.on.net 1221981493 J * Bruno ~Bruno@207.35.94.45 1221981744 Q * BrunoXLambert Ping timeout: 480 seconds 1221981921 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d 1221982641 J * ntrs_ ~ntrs@77.29.72.90 1221983060 Q * ntrs Ping timeout: 480 seconds 1221986712 J * hparker ~hparker@linux.homershut.net 1221989485 Q * hparker Quit: Read error: 104 (Peer reset by connection) 1221989648 J * SlackLnx ~Lee@bl7-150-143.dsl.telepac.pt 1221991300 J * cga ~weechat@host-84-221-254-115.cust-adsl.tiscali.it 1221991511 Q * derjohn_foo Ping timeout: 480 seconds 1221992957 Q * bonbons Quit: Leaving 1221995059 J * dna ~dna@159-213-dsl.kielnet.net 1221997180 Q * Aiken Remote host closed the connection 1222000643 Q * friendly Remote host closed the connection 1222001314 N * Bertl_zZ Bertl_oO 1222002763 Q * cga Quit: WeeChat 0.2.6 1222003704 J * mrfree ~mrfree@host37-179-dynamic.13-79-r.retail.telecomitalia.it 1222004261 J * ntrs__ ~ntrs@77.29.78.41 1222004658 Q * Bruno Remote host closed the connection 1222004686 J * BrunoXLambert ~Bruno@207.35.94.45 1222004688 Q * ntrs_ Ping timeout: 480 seconds 1222004846 Q * BrunoXLambert 1222007916 J * BrunoXLambert ~Bruno@207.35.94.45 1222011502 J * derjohn_foo ~aj@e180201028.adsl.alicedsl.de 1222014182 J * cga ~weechat@85-18-201-166.ip.fastwebnet.it 1222014545 Q * cga Quit: WeeChat 0.2.6 1222016996 J * hparker ~hparker@linux.homershut.net 1222018192 Q * doener_ Quit: leaving 1222018589 J * doener ~doener@i577BA3C6.versanet.de 1222019949 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d 1222020749 J * vserveruser ~ben@cpc3-stre3-0-0-cust635.bagu.cable.ntl.com 1222020753 M * vserveruser Hi gues 1222020755 M * vserveruser *guys 1222020786 M * vserveruser I'm having a little bother with my vservers, most notably my mail one, which will run for around 24 hours, then the network adaptor will just disappear 1222020802 M * vserveruser I'm running 2.6.26-bpo.1-vserver-686 1222020824 M * Bertl_oO network adapters do not disappear suddenly :) 1222020826 M * vserveruser A `vserver mail reboot`, fixes it - but this is far from ideal 1222020832 M * vserveruser trust me, it does 1222020842 M * Bertl_oO trust me, it doesn't :) 1222020870 M * Bertl_oO first, a default guest does not have _any_ access to the network interfaces 1222020874 M * vserveruser a list of the current ethernet adapters will just show the loopback 1222020897 M * Bertl_oO second, all address adding/removing happens on the host 1222020905 M * vserveruser The host operates fine 1222020916 M * vserveruser its inside the vserver itself, its eth0 just disappears 1222020924 M * vserveruser running ifup eth0 gives an error 1222020926 M * Bertl_oO so, my guess is that something on the host 'decides' to restart one of your interfaces 1222020947 M * Bertl_oO maybe ifplugd or so? and thus the ip assigned to the guest 'disappears' 1222020947 M * vserveruser any logs I could check to confirm this 1222020978 M * Bertl_oO once the ip is gone (i.e. not assigned to the interface) the interface will not be visible anymore (inside the guest) 1222020998 M * daniel_hozac /var/log/messages on the host. 1222020999 M * Bertl_oO check /var/log/messages on the host 1222021002 M * daniel_hozac my bet would be dhclient. 1222021005 M * Bertl_oO :) 1222021034 M * daniel_hozac or, well, it's Debian, so /var/log/syslog is probably better. 1222021034 M * vserveruser last log in there is from sep 12th 1222021053 M * vserveruser in both 1222021069 M * vserveruser and the date is correct on the server 1222021113 M * daniel_hozac so you don't use DHCP? 1222021157 M * Bertl_oO a flakey network line can cause that (with ifplugd) too 1222021170 M * vserveruser no, ips are static in /etc/network/interfaces 1222021177 M * daniel_hozac yeah, true. 1222021186 M * daniel_hozac so make sure they're auto and not allow-hotplug. 1222021216 M * vserveruser auto eth0:4 1222021216 M * vserveruser iface eth0:4 inet static 1222021216 M * vserveruser address 89.XXX.XXX.XXX 1222021216 M * vserveruser netmask 255.255.255.0 1222021233 M * daniel_hozac so they're _all_ auto, even eth0? 1222021238 M * vserveruser yeah 1222021251 M * vserveruser auto lo 1222021251 M * vserveruser iface lo inet loopback 1222021251 M * vserveruser # The primary network interface 1222021251 M * vserveruser auto eth0 1222021251 M * vserveruser iface eth0 inet static 1222021252 M * vserveruser address 89.16.177.95 1222021260 M * vserveruser etc 1222021485 M * vserveruser any thoughts? 1222021516 M * vserveruser I don't have to reset networking on the host, simply resetting the vhost does the trick 1222021550 M * daniel_hozac the host's IPs are taken care of by the host, guest IPs are taken care of by util-vserver. 1222021554 M * daniel_hozac unless you're using nodev. 1222021563 M * vserveruser ...no dev? 1222021726 M * daniel_hozac i'd take that as a no :) 1222021737 M * vserveruser I don't know what nodev is 1222021750 M * daniel_hozac is (r)syslogd running on the host? 1222021768 M * vserveruser I would imagine so 1222021784 M * daniel_hozac the default Debian install will log something every 20 minutes to messages. 1222021811 M * daniel_hozac so no entries since september 12th suggests something's broken. 1222021855 M * vserveruser apt-get install rsyslogd ? then 1222021865 M * daniel_hozac i would hope it's already installed. 1222021876 M * vserveruser nope :( 1222021884 M * vserveruser its installed now 1222021884 M * daniel_hozac and neither is sysklogd? 1222021896 M * vserveruser nope 1222021899 M * vserveruser installed now too 1222021910 M * daniel_hozac ... you can only use one of them. 1222021916 M * vserveruser lol 1222021925 M * vserveruser which is better 1222021941 Q * derjohn_foo Ping timeout: 480 seconds 1222021982 M * daniel_hozac rsyslog is the "newer" one, but i don't think it differs significantly from sysklogd. 1222022012 M * vserveruser so next time something out of the ordinary happens... 1222022018 M * vserveruser i take it i need to check the error logs 1222022028 M * daniel_hozac that is always a good idea... 1222022035 M * vserveruser right :( 1222022045 M * vserveruser i'll come back in 24hrs when it bombs again 1222022051 M * vserveruser thanks mate! 1222022070 M * daniel_hozac you're welcome! 1222023513 Q * vserveruser Ping timeout: 480 seconds 1222025541 J * lilalinux ~plasma@80.69.41.3 1222025745 J * Aiken ~Aiken@ppp118-208-28-181.lns2.bne1.internode.on.net 1222025879 J * ntrs_ ~ntrs@77.29.74.0 1222026142 M * snooze what defines where the vservers.conf is placed? and is the conf actually needed? all i have inside is BACKGROUND=no 1222026187 M * daniel_hozac that's a legacy file. 1222026211 M * snooze so i could simply delete it? :) 1222026222 M * daniel_hozac if you're not using the legacy stuff, yes. 1222026231 M * snooze what would the legacy stuff be? 1222026250 M * daniel_hozac /etc/vservers/.conf 1222026277 M * snooze each one has a dir 1222026308 Q * ntrs__ Ping timeout: 480 seconds 1222026311 M * daniel_hozac then you're not using the legacy configurations. 1222026327 M * snooze :) 1222026329 M * snooze thanks 1222026803 Q * lilalinux Remote host closed the connection 1222026979 J * cryptronic ~oli@p4FD2FA2E.dip.t-dialin.net 1222028001 J * wam ~wam@p5B2FF074.dip.t-dialin.net 1222028033 M * wam Why are there not kernel patches for newer kernel versions? 1222028254 M * Wonka not yet developed. 1222028265 M * daniel_hozac 2.6.27 is out already? 1222028284 M * snooze nope 1222028286 M * Wonka http://www.kernel.org/ says not 1222028304 M * daniel_hozac so what "newer kernel versions" is that in reference to? 1222028321 Q * bonbons Quit: Leaving 1222028344 M * Wonka newer than 2.6.22.19 maybe 1222028361 M * daniel_hozac the most recent patch is 2.6.26.5-vs2.3.0.35.6... 1222028404 M * Wonka http://vserver.13thfloor.at/Experimental/patch-2.6.26.5-vs2.3.0.35.6.diff is experimental and not linked on the linux-vserver.org front page... 1222028425 M * Wonka clear case of not reading properly, i'd say 1222028484 M * wam Wonka: I already used experimental releases. But why isn't this linked to the frontpage? Are there concerns about the stability? 1222028497 M * daniel_hozac it's not yet feature complete. 1222028505 M * Wonka that's what "experimental" could mean 1222028567 M * wam daniel_hozac: feature complete as "not all planned features included" or as "not all features as in the last version included"? 1222028593 M * daniel_hozac not all features have been ported to the newer kernels yet. 1222028598 M * wam ok 1222028647 M * wam I was just wondering, because there was some discussion some months ago, if linux will include code for virtualization and linux-vserver was contributing code. What I feared was that linux included some other virtualization code and linux-vserver is behind its time because it has to use that. 1222028918 J * derjohn_foo ~aj@p5B23E823.dip.t-dialin.net 1222030904 M * wam does anyone know about a project that uses linux-vserver in a cloud computing environment? 1222031573 J * jklblerf jkl@c-75-70-178-175.hsd1.co.comcast.net 1222031580 M * jklblerf good afternoon, 1222031591 M * jklblerf does anyone know how to disable the multicast flag inside a vserver? 1222031612 N * jklblerf jkl 1222032356 M * daniel_hozac what multicast flag? 1222032432 Q * ntrs_ Ping timeout: 480 seconds 1222033715 Q * mrfree Quit: Leaving 1222033776 Q * wam Remote host closed the connection 1222034320 J * doener_ ~doener@i577B9DD6.versanet.de 1222034461 Q * doener Read error: Connection reset by peer 1222034981 J * cga ~weechat@host-84-221-254-115.cust-adsl.tiscali.it 1222035760 J * vserveruser ~ben@cpc3-stre3-0-0-cust635.bagu.cable.ntl.com 1222037009 Q * cga Quit: WeeChat 0.2.6 1222037184 Q * dna Quit: Verlassend 1222039528 Q * hparker Quit: Read error: 104 (Peer reset by connection) 1222039702 J * hparker ~hparker@linux.homershut.net 1222039710 Q * hparker Read error: Connection reset by peer 1222040188 J * hparker ~hparker@linux.homershut.net