1296087105 Q * bonbons Quit: Leaving
1296089411 Q * fzylogic Ping timeout: 480 seconds
1296090245 J * fzylogic ~fzylogic@208.80.64.79
1296094083 Q * bsingh Read error: Operation timed out
1296094829 J * bsingh ~balbir@122.172.44.185
1296095218 J * ktwilight ~keliew@91.176.121.10
1296095481 Q * ktwilight__ Ping timeout: 480 seconds
1296096565 Q * hparker Quit: Quit
1296096581 Q * bsingh Ping timeout: 480 seconds
1296102233 J * kir1 ~kir@swsoft-msk-nat.sw.ru
1296106751 N * Bertl_zZ Bertl
1296106756 M * Bertl morning folks!
1296112752 M * hijacker morning
1296114183 Q * Piet Remote host closed the connection
1296114238 J * Piet ~Piet__@82VAABMRB.tor-irc.dnsbl.oftc.net
1296114468 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com
1296115533 Q * Piet Ping timeout: 480 seconds
1296116121 J * Piet ~Piet__@82VAABMR7.tor-irc.dnsbl.oftc.net
1296117582 M * arekm er
1296118370 Q * jeroen_ Quit: Ex-Chat
1296118712 P * kir1 Leaving.
1296118985 J * jeroen_ ~jeroen@imap.powerinternet.eu
1296120325 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d
1296121409 Q * DLange Quit: rebuuuuuuuuut....
1296121556 J * DLange ~DLange@dlange.user.oftc.net
1296121665 J * petzsch ~markus@dslb-092-078-157-073.pools.arcor-ip.net
1296123376 Q * nkukard Read error: Operation timed out
1296123473 J * nkukard ~nkukard@41-133-112-137.dsl.mweb.co.za
1296123482 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647
1296126897 Q * hparker Quit: Quit
1296130054 M * Bertl nap attack ... bbl
1296130075 N * Bertl Bertl_zZ
1296131579 Q * Chlorek Ping timeout: 480 seconds
1296131619 Q * cokolwiek Ping timeout: 480 seconds
1296132104 J * Chlorek ~cokolwiek@c.sed.pl
1296132111 N * Chlorek cokolwiek
1296132114 J * tymczas0 nobody@2001:6a0:183:f002::3
1296132131 N * tymczas0 Chlorek
1296133261 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647
1296135994 Q * Mr_Smoke Ping timeout: 480 seconds
1296136979 J * thierryp ~thierry@zankai.inria.fr
1296140947 N * Bertl_zZ Bertl
1296142143 J * Huendchen josef@ip-95-223-36-117.unitymediagroup.de
1296142146 M * Huendchen vdu: lstat("mysql-dropdb.sh"): Stale NFS file handle <- wtf?!
1296142389 M * Bertl seems like your nfs server changed somehow
1296143197 Q * Piet Remote host closed the connection
1296143239 M * Huendchen whats the command for shuting down all vservers? 
1296143705 M * Bertl AFAIK, there is no generic command to shut down all guests .. if they have a mark set, you can use that to shut them down as done in the runlevel scripts, otherwise, something like:
1296143716 M * Bertl for n in `(cd /etc/vservers; /bin/ls )`; do vserver $n stop; done
1296143716 Q * thierryp Remote host closed the connection
1296143719 M * Bertl should work
1296144360 J * Piet ~Piet__@82VAABM2E.tor-irc.dnsbl.oftc.net
1296145070 M * ser hi, i do not have a remote kvm access to the server, so to have a better control in unpredictable situations,i am thinking to deploy xen in between vserver host and hardware
1296145110 M * ser my only concern is there is only (do not ask why) one kernel available for xen: 2.6.27
1296145132 M * Bertl you mean, as dom0 kernel, yes?
1296145135 M * ser do you think it is not too old for a modern hadrware?
1296145138 M * ser yes
1296145167 M * Bertl no idea if that is too old or if it will work reasonably well as dom0, I wouldn't even touch a 2.6.27 kernel :)
1296145171 M * ser i can install 2.6.36 without xen
1296145183 M * ser ok i can see
1296145194 M * ser thanks, it helps a lot
1296145223 M * ser <3
1296145840 M * ser but, with a modern kernel, xen on the top of single vserver host should be a reasonable solution, should not it?
1296145859 M * ser i mean minimal overhead?
1296145927 M * daniel_hozac i gotta ask, why xen rather than something like kvm?
1296146028 M * ser to be honest for me it does not matter, i just need a strong base for vserver platform
1296146061 M * ser i know xen a little bit, so it was a first idea i got
1296146096 M * Bertl I don't see how adding xen to the mix would make the 'base' stronger?
1296146103 M * ser if you think other solutions may be more stable and/or with less overhead?
1296146144 M * ser for example kernel upgrade with vserver host?
1296146161 M * ser i can protect xen base on firewall very strictly
1296146189 M * ser which makes it more secure then not updated vserver host kernel
1296146221 M * ser i am just thinking loudly, if i am wrong, please correct me
1296146788 M * ser i cannot see any reaction, does it mean i am deploying science-fiction?
1296146841 M * Bertl let's assume there is a kernel bug which is related to networking (and some network exploit)
1296146874 M * Bertl so, the idea is to use the xen kernel to 'shield' the vserver host kernel from an exploit
1296146907 M * Bertl but hey, most likely the xen dom0 is much older than the Linux-VServer kernel, and thus will be vulnerable to exactly that kernel exploit, no?
1296146921 M * ser hmmm
1296147004 M * ser yes, but please notice i can handle upgrade of linux-vserver kernel without any risk associated with any such action, because i can login into the machine and rescue it
1296147079 M * ser of course kvm would be better, but there is no kvm
1296147123 M * Bertl why not get a serial console?
1296147170 M * ser it is a server i cannot modify/add hardware :( i can only think out software solutions. 
1296147203 M * ser a black box, let us say
1296147443 M * Bertl well, even black boxes usually have serial ports :)
1296147474 M * Bertl but how to upgrade e.g. the dom0 without kvm/console
1296147625 M * ser yes, it is an issue, because xen on the top gives only some time to secure essential services put under the risk with vserver kernel
1296147639 M * ser ok, thanks a lot - i will re-think it :)
1296147749 M * Bertl so IMHO you are probably better off if you find a hosting solution where you can connect a serial cable to the machine
1296147775 M * Bertl usually that is not a problem if you get two physical machines in the same place (for redundancy) and connect them via serial
1296148157 M * ser yes, indeed, i will try to convince my customer
1296148172 M * ser thanks for your patience :)
1296148242 M * Bertl no problem ...
1296148830 J * jrdnyquist ~jrdnyquis@slayer.caro.net
1296150273 J * imcsk8 ~ichavero@148.229.1.11
1296150642 N * ensc Guest1841
1296150652 J * ensc ~irc-ensc@p5DF2C8A9.dip.t-dialin.net
1296150749 Q * Guest1841 Ping timeout: 480 seconds
1296151254 J * hijacker_ ~hijacker@87-126-142-51.btc-net.bg
1296156287 J * dna ~dna@dslb-088-074-210-189.pools.arcor-ip.net
1296156816 J * manana ~mayday090@84.17.25.149
1296159691 J * yarihm ~yarihm@178-83-213-36.dynamic.hispeed.ch
1296160610 J * raanders ~raanders@hugin.cyber-office.net
1296162073 Q * manana Ping timeout: 480 seconds
1296162107 Q * Piet Remote host closed the connection
1296163238 J * Piet ~Piet__@82VAABNAJ.tor-irc.dnsbl.oftc.net
1296164009 Q * hijacker_ Quit: Leaving
1296164286 Q * dna Quit: Verlassend
1296164923 Q * hparker Quit: Quit
1296165865 Q * yarihm Quit: This computer has gone to sleep
1296165906 Q * petzsch Quit: Leaving.
1296166274 J * petzsch ~markus@dslb-092-078-157-073.pools.arcor-ip.net
1296167203 Q * petzsch Quit: Leaving.
1296168039 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647
1296168808 Q * FireEgl Remote host closed the connection
1296169232 Q * Piet Remote host closed the connection
1296169375 J * Piet ~Piet__@659AAB5X5.tor-irc.dnsbl.oftc.net
1296170787 M * Bertl off to bed now ... have a good one everyone!
1296170792 N * Bertl Bertl_zZ
1296171226 Q * hparker Quit: Quit
1296171719 Q * bonbons Quit: Leaving
1296171853 P * raanders 
1296171960 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647
1296172506 Q * imcsk8 Quit: Leaving