1232841741 Q * bonbons Quit: Leaving
1232841866 M * Bertl you're welcome!
1232842870 Q * nou Ping timeout: 480 seconds
1232843879 J * friendly ~friendly@ppp118-208-214-49.lns10.mel6.internode.on.net
1232844595 Q * ousado__ Ping timeout: 480 seconds
1232845431 Q * hparker Ping timeout: 480 seconds
1232845767 J * nou Chaton@causse.larzac.fr.eu.org
1232846509 Q * geb Quit: Quitte
1232846697 Q * Aiken Quit: Leaving
1232847092 J * hparker ~hparker@2001:470:1f0f:32c:212:f0ff:fe0f:6f86
1232852131 J * Piet_ ~piet@asteria.debian.or.at
1232852450 Q * nenolod Ping timeout: 480 seconds
1232852500 Q * Piet Ping timeout: 480 seconds
1232852674 J * nenolod nenolod@petrie.dereferenced.org
1232853468 J * Tito ~Tito@tito.prolink.org
1232854197 N * AfterDeath adth
1232855150 Q * Tito 
1232856078 Q * Piet_ Quit: Piet_
1232860591 M * Bertl off to bed now ... have a good one everyone!
1232860597 N * Bertl Bertl_zZ
1232862117 Q * infowolfe Remote host closed the connection
1232862300 J * infowolfe ~infowolfe@c-24-21-204-37.hsd1.or.comcast.net
1232862949 Q * nenolod Ping timeout: 480 seconds
1232863789 J * nenolod nenolod@petrie.dereferenced.org
1232865034 Q * hparker Quit: Read error: 104 (Peer reset by connection)
1232866051 J * Aiken ~Aiken@ppp118-208-45-4.lns3.bne1.internode.on.net
1232869528 Q * friendly Quit: Leaving.
1232870207 Q * miller7 
1232873141 J * ousado__ ~johnny@frnk-5f743d17.pool.einsundeins.de
1232876451 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d
1232878116 J * dna ~dna@39-199-103-86.dynamic.dsl.tng.de
1232878582 N * pmenier_off pmenier
1232879210 Q * bonbons Quit: Leaving
1232879805 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d
1232882106 Q * bonbons Quit: Leaving
1232882538 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d
1232883683 J * cga ~weechat@94.36.93.49
1232884124 J * Piet ~piet@asteria.debian.or.at
1232885340 Q * Aiken Quit: Leaving
1232885554 J * Tito ~Tito@tito.prolink.org
1232887089 Q * Piet Quit: Piet
1232888464 Q * docelic__ Quit: http://www.spinlocksolutions.com/
1232888938 J * geb ~geb@AOrleans-151-1-72-25.w90-21.abo.wanadoo.fr
1232888974 M * geb hi
1232891790 N * Bertl_zZ Bertl
1232891799 M * Bertl morning folks!
1232892562 J * geb_ ~geb@AOrleans-151-1-5-8.w90-21.abo.wanadoo.fr
1232892676 Q * geb Ping timeout: 480 seconds
1232893246 Q * geb_ Quit: Quitte
1232894221 J * Piet ~piet@asteria.debian.or.at
1232895489 J * takeru ~takeru@nttkyo888227.tkyo.nt.ftth.ppp.infoweb.ne.jp
1232896938 M * fb morning Bertl!
1232897014 M * pmenier Hello
1232897046 M * pmenier little problem... can't start a newly created vserver
1232897058 M * pmenier http://www.pmenier.net/vserver/26281/config26281-vm
1232897141 M * ktwilight__ pmenier, try the latest util-vserver
1232897152 M * ktwilight__ at least 0.30.216
1232897167 M * ktwilight__ oh wait, my bad.
1232897171 M * pmenier ah ok
1232897183 M * ktwilight__ you actually need a service in the runlevel inside raidvs1
1232897195 M * ktwilight__ doesn't seem like you have one.
1232897223 M * pmenier it would have at least syslog no ?
1232897297 M * ktwilight__ yea
1232897318 M * pmenier ktwilight__: you're right: no services in /etc/rc*.d ...
1232897519 M * pmenier now i get: /etc/init.d/rc: line 221: /etc/rc3.d/S10ksyslogd: Permission denied
1232897556 M * ktwilight__ check file perm
1232897663 M * pmenier good, thanks, it runs now
1232897723 M * ktwilight__ :)
1232897782 Q * takeru Quit: takeru
1232897873 J * Hunger Hunger.hu@Hunger.hu
1232897874 Q * Hunger Remote host closed the connection
1232898269 J * Hunger Hunger.hu@Hunger.hu
1232900496 J * geb ~geb@AOrleans-151-1-5-8.w90-21.abo.wanadoo.fr
1232900807 J * beefcake ~543ae088@67.159.35.76
1232901020 Q * beefcake 
1232901785 J * hparker ~hparker@2001:470:1f0f:32c:212:f0ff:fe0f:6f86
1232902076 J * _Hunger CCC@Hunger.hu
1232902302 Q * Hunger Ping timeout: 480 seconds
1232902458 Q * Piet Remote host closed the connection
1232902531 J * Piet ~piet@asteria.debian.or.at
1232902568 Q * _Hunger Ping timeout: 480 seconds
1232902854 J * derjohn ~derjohn@80.69.41.3
1232903619 J * yarihm ~yarihm@77-56-182-18.dclient.hispeed.ch
1232904471 J * _Hunger Hunger.hu@Hunger.hu
1232904534 N * _Hunger Hunger
1232905077 Q * Hunger Ping timeout: 480 seconds
1232906196 Q * mcp Remote host closed the connection
1232906274 J * mcp ~mcp@wolk-project.de
1232907395 Q * nou Ping timeout: 480 seconds
1232908183 J * Hunger Hunger.hu@Hunger.hu
1232908184 Q * Hunger Max SendQ exceeded
1232908257 J * Hunger Hunger.hu@Hunger.hu
1232910982 Q * harry Quit: new kernel...
1232912111 Q * geb Quit: Quitte
1232912297 J * harry ~harry@d51A461B4.access.telenet.be
1232913232 J * nou Chaton@causse.larzac.fr.eu.org
1232914239 J * balbir_ ~balbir@122.172.54.77
1232914265 N * balbir_ identify
1232914293 N * pmenier pmenier_off
1232914315 N * identify balbir_
1232914593 M * Guy- hmm, just idly wondering: it's not possible to start a 64bit guest on a host with a 64bit kernel, but 32bit userspace, right?
1232914609 M * Guy- (amd64 kernel with i386 userspace on host, amd64 userspace in guest)
1232914632 M * Bertl I think it is possible, but it will be tricky
1232914685 M * Guy- tricky how?
1232914715 M * Bertl 64bit executables should execute fine, even from a 32bit shell
1232914747 M * Bertl so, the problem is more to get the guest personality right
1232914789 M * Guy- which means fiddling with uts somehow?
1232914813 M * Bertl well, give it a try, see what fails, if anything at all
1232914825 M * Bertl avoid setting personality explicitely
1232914861 M * Guy- I was actually just relaying the question, but I'll have my colleague try then, thanks :)
1232914909 Q * cga Quit: WeeChat 0.2.6
1232915960 Q * Tito 
1232920194 M * ktwilight__ 2.6.27.13 and 2.6.28.2 are out
1232923291 Q * dna Quit: Verlassend
1232923999 M * Bertl ktwilight__: tx, patches are updated :)
1232924030 J * ser ~ser@sergiusz.pawlowicz.name
1232924042 M * Bertl welcome ser!
1232924072 M * ser hello, i'd like to slow down our mail vserver when other vmachines are busy, what is the best way to do it? just nice"
1232924075 M * ser ?
1232924147 M * Bertl there is a so called priority bias (i.e. a nice offset) per guest
1232924173 M * Bertl you should be able to adjust the priorities using that
1232924177 M * ser you mean /etv/vservers/.../nice ?
1232924183 M * ser or which parameter?
1232924204 M * Bertl http://www.nongnu.org/util-vserver/doc/conf/configuration.html
1232924219 M * Bertl search for 'priority-bias'
1232924224 M * ser thanks
1232924228 M * Bertl np
1232924306 Q * ruin_ Quit: leaving
1232924496 M * ser so what's about possible values of priority-bias - e.g. what does it mean "1" value?
1232924558 M * Bertl consider priority working the other way than niceness
1232924580 M * Bertl as it is a bias, it gets added to the 'normal' values
1232924625 M * ser ok so "1"  means it would "simulate" it is slightly more loaded?
1232924819 T * * http://linux-vserver.org/ |stable 2.2.0.7, devel 2.3.0.34, grsec 2.3.0.36|util-vserver-0.30.215|libvserver-1.0.2|vserver-utils-1.0.3| He who asks a question is a fool for a minute; he who doesn't ask is a fool for a lifetime -- share the gained knowledge on the Wiki, and we forget about the minute.
1232924819 T * Bertl -
1232924870 M * Bertl a value of "1" would increase that guest's priority slightly above others
1232924888 F * Bertl -o Bertl
1232924914 M * ser OK, but if /etv/vservers/.../nice for both of them is 19, does it matter?
1232924924 M * Bertl yes
1232925025 Q * yarihm Quit: Leaving
1232925073 M * ser by the above sentence you mean other servers in such a conditions will get slightly less resources, right?
1232925098 M * ser other then this with "1"
1232925120 M * Bertl yes, that is what the scheduler does
1232925148 J * lownoize_ ~lownoize@swt32.informatik.uni-mannheim.de
1232925155 N * lownoize_ lownoize
1232925158 M * lownoize hi
1232925166 M * Bertl hey
1232925251 M * lownoize i have a really strange problem, moved some vservers from host a to host b, and all work fine, except of one. when i try to start it i just get Failed to start vserver 'internal' 
1232925273 M * lownoize and nothing else, is there a way to get a more verbose output?
1232925298 M * Bertl try with --debug
1232925347 M * ser Bertl: last question in this series: what is the difference between e.g. "3" and "1" in priority-bias?
1232925362 M * Bertl 2 :)
1232925380 M * ser good answer but does it mean 200% or what
1232925395 M * ser how is it counted :)
1232925397 J * jfs ~jfs@ip-80-236-204-76.dsl.scarlet.be
1232925406 M * Bertl good question, but that really depends
1232925414 M * lownoize thanks Bertl, i found the error ;)
1232925437 M * Bertl ser: the linux scheduler maps processes according to different factors to so called priorities
1232925463 M * ser Bertl: are there any whitepapers about this priority-bias stuff on www?
1232925468 M * Bertl ser: if you look with ps auxwww or (h)top, you'll see that processes have a nice value _and_ a priority
1232925489 M * Bertl the nice value is kind of given/fixed, the priority is calculated
1232925527 M * Bertl the priority is used for scheduling decisions, and the priority bias shifts the calculated priority within the permissible bounds
1232925536 M * lownoize was my broken scrip in pre-start.d
1232925543 M * Bertl lownoize: excellent!
1232925553 M * ser lownoize: well done!
1232925578 M * Bertl ser: so get some whitepaper on the 'priority calculation' of the Linux scheduler, and just add 'priority bias' to the result
1232925608 M * ser Bertl: ok, thanks!
1232925609 M * Bertl the overall effect might be 2% or 2000% depending on the actual situation
1232925644 M * Bertl but in general you can assume that a higher priority bias will give more cpu resources to the guest
1232925679 J * opuk_ ~kupo@potatisbulle.com
1232925694 M * ser is it ease to manage i/o stuff the same way?
1232925740 M * Bertl not really, I/O is always tricky
1232925780 M * ser  ;-(
1232925797 Q * opuk Ping timeout: 480 seconds
1232925855 M * Bertl ser: what kernel are you using?
1232925959 M * ser last lenny vserver i hope
1232925977 M * Bertl no idea what kernel/patches that is ...
1232926009 J * geb ~geb@79.82.4.55
1232926013 M * ser # vserver-info 
1232926013 M * ser Versions:
1232926013 M * ser                    Kernel: 2.6.26-1-vserver-amd64
1232926013 M * ser                    VS-API: 0x00020303
1232926014 M * ser              util-vserver: 0.30.216-pre2772; Aug 27 2008, 21:40:37
1232926039 M * geb hu
1232926049 M * Bertl so, that is a 2.6.26 kernel, with a 2.3.x API
1232926144 Q * ousado__ Ping timeout: 480 seconds
1232926179 M * ser so to slow down one of vservers i can put "-1" as priority-bias?
1232926184 M * Bertl on the stable series, you could have used the cfq to separate/equalize the I/O, on that one the only thing you can do is reduce the overall I/O (if that causes problems)
1232926203 M * Bertl ser: yes, for the cpu part
1232926254 M * ser how can i reduce overall I/O on particular vserver?
1232926279 M * Bertl not just on the guest, on the host .. assumed that you actually have I/O related issues
1232926316 M * Bertl do you get a lot of '%wa' in top?
1232926331 M * ser htop
1232926429 M * ser i cannot say now if i have big wa as traffic is approching only once on different hour
1232926452 M * ser but ok, i am starting to understand
1232926455 M * lownoize time to install sysstat
1232926464 M * ser lownoize: dstat
1232926476 J * doener_ ~doener@i577B9657.versanet.de
1232926580 Q * doener Ping timeout: 480 seconds
1232926678 M * lownoize has dstat something like sar?
1232926785 M * ser i think it could write into a file
1232926792 M * ser but i did not try
1232926831 M * lownoize but dstat looks really nice
1232926954 J * ousado__ ~johnny@frnk-5f743d17.pool.einsundeins.de
1232927005 M * ser it's amazing, as htop's companion
1232927447 Q * ousado__ Ping timeout: 480 seconds