1262823755 J * SubZero ~SubZero@chello089076140236.chello.pl
1262826105 Q * dowdle Remote host closed the connection
1262827805 Q * scientes Ping timeout: 480 seconds
1262830723 J * SteveJhonson ~Kable@190.51.136.134
1262832728 N * SteveJhonson hel
1262832731 N * hel help
1262832924 N * help SteveJhonson
1262833142 Q * Piet Remote host closed the connection
1262833197 Q * SteveJhonson Quit: bye
1262833243 J * derjohn_foo ~aj@e180193048.adsl.alicedsl.de
1262833673 Q * derjohn_mob Ping timeout: 480 seconds
1262835119 Q * imcsk8 Quit: Leaving
1262835278 J * aj__ ~aj@e180192141.adsl.alicedsl.de
1262835472 Q * derjohn_foo Ping timeout: 480 seconds
1262836845 J * saulus_ ~saulus@d003241.adsl.hansenet.de
1262837224 Q * SauLus Ping timeout: 480 seconds
1262837230 N * saulus_ SauLus
1262837614 Q * Guest1 Read error: Connection reset by peer
1262837623 J * ensc ~irc-ensc@77.235.160.26
1262837638 Q * aj__ Ping timeout: 480 seconds
1262840528 Q * YEP Read error: Connection reset by peer
1262841575 J * geb ~geb@earth.gebura.eu.org
1262844373 Q * niki Quit: Leaving
1262844642 M * geb hi
1262844774 M * theocrite hi
1262844942 M * Bertl off to bed now ... have a good one everyone!
1262844948 N * Bertl Bertl_zZ
1262844957 M * theocrite Good night Bertl_zZ 
1262845865 M * Mr_Smoke mo'in
1262846261 J * balbir ~balbir@122.172.145.96
1262847444 J * aj__ aj@88.128.90.152
1262848479 J * ghislain ~AQUEOS@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr
1262849948 Q * SkyC Ping timeout: 480 seconds
1262850712 J * niki ~niki@cpe.fe4-0-120.0x50a6de52.kdnxd4.customer.tele.dk
1262851380 J * sharkjaw ~gab@90.149.121.45
1262852214 M * pmjdebruijn ah
1262852219 M * pmjdebruijn 2.6.27.43 has been released
1262853315 Q * hijacker__ Read error: Connection reset by peer
1262853360 J * hijacker__ ~hijacker@213.91.163.5
1262853647 Q * aj__ Ping timeout: 480 seconds
1262854064 J * SkyC ~Administr@cpe-65-31-31-119.insight.res.rr.com
1262854130 Q * balbir Ping timeout: 480 seconds
1262854680 J * davidkarban ~david@80.250.18.198
1262854789 J * balbir ~balbir@122.172.57.129
1262855114 J * thierryp ~thierry@zankai.inria.fr
1262859719 J * barismetin ~barismeti@zanzibar.inria.fr
1262860222 J * gnuk ~F404ror@pla93-3-82-240-11-251.fbx.proxad.net
1262861145 J * aj__ ~aj@213.238.45.2
1262862022 J * shedi ~siggi@host90-152-67-98.ipv4.regusnet.com
1262862050 M * shedi hi vserver channel
1262862090 M * shedi I have a process running secure-mount, that hangs, eats up my cpu, and can't be killed
1262862135 Q * niki Remote host closed the connection
1262862162 M * shedi util-vserver 0.30.216~r2772-6 
1262862176 M * shedi 2.6.26-2-vserver-amd64
1262862222 M * shedi the process has a R status, but still I can't kill it
1262862249 M * shedi I was using option bind in the vserver fstab
1262862941 J * dna ~dna@32-199-103-86.dynamic.dsl.tng.de
1262863086 M * daniel_hozac try a more recent version
1262863506 M * shedi is there any way to kill the damned thing SIGKILL and SIGSTOP don't affect it at all
1262863516 M * shedi or block it
1262864153 M * ^Willie^ kill -9 pid 
1262864154 M * ^Willie^ ?
1262864212 M * shedi does not work
1262865801 J * yarihm ~yarihm@217-162-53-251.dclient.hispeed.ch
1262866927 Q * davidkarban Quit: Ex-Chat
1262868371 Q * balbir Read error: Connection reset by peer
1262869296 J * balbir ~balbir@122.172.48.63
1262870713 Q * shedi Quit: Leaving
1262870835 Q * SubZero 
1262871495 J * elesouef_ ~elesouef@212.51.177.50
1262871495 Q * elesouef Remote host closed the connection
1262871940 Q * elesouef_ Quit: leaving
1262873045 J * jrklein ~jrklein@2001:0:53aa:64c:0:44ad:b4d8:690
1262873631 Q * gnuk Quit: NoFeature
1262874037 J * docelic ~docelic@78-2-127-241.adsl.net.t-com.hr
1262874602 Q * sharkjaw Remote host closed the connection
1262874993 Q * docelic Quit: http://www.spinlocksolutions.com/
1262875933 Q * geb Ping timeout: 480 seconds
1262876133 J * kolorafa ~kolorafa@byd220.neoplus.adsl.tpnet.pl
1262876451 M * kolorafa hi, thx, and sorry for taking your time - sched 'problem' - http://kolorafa.pl/problem.txt
1262878265 J * Piet ~Piet__@659AAAWDK.tor-irc.dnsbl.oftc.net
1262879203 Q * Piet Ping timeout: 480 seconds
1262879302 J * Piet ~Piet__@659AAAWDX.tor-irc.dnsbl.oftc.net
1262879347 J * jamiem_ ~jamie@lair.fifthhorseman.net
1262879403 Q * kolorafa Ping timeout: 480 seconds
1262879412 M * jamiem_ I understand that I can't remove a single ip from a vserver using naddress. How do I remove all IP addresses so I can only put back in the ones I want to keep (as references here: http://www.paul.sladen.org/vserver/archives/200907/0061.html)?
1262879745 Q * Piet Remote host closed the connection
1262879932 J * dowdle ~dowdle@scott.coe.montana.edu
1262880133 J * Piet ~Piet__@659AAAWEG.tor-irc.dnsbl.oftc.net
1262880295 Q * yarihm Quit: This computer has gone to sleep
1262881535 N * Bertl_zZ Bertl
1262881539 M * Bertl morning folks!
1262881746 Q * nkukard Remote host closed the connection
1262881759 M * ^Willie^ noon
1262881920 J * nkukard ~nkukard@196.212.73.74
1262881955 J * pinochle ~pinochle@67.159.48.101
1262882001 M * pinochle im running dahdi (Asterisk kernel module) on a host node, and ive created the /dev/dahdi/* devices in the VE, but the VE does not include the /proc entries 
1262882027 M * pinochle any way i can link the VE's /proc/dahdi/* to the Host's
1262882096 M * Bertl jamiem_: naddress --remove
1262882118 M * jamiem_ thanks. does that remove for all vservers on the host?
1262882134 M * Bertl pinochle: you need to change the proc hiding set (and it will affect all guests)
1262882178 M * Bertl jamiem_: it will not remove any address from the host, it will only remove address(es) from guests
1262882192 M * jamiem_ yes - right. thanks for clarifying.
1262882206 M * pinochle Bertl: where does that take place Bertl?
1262882278 M * Bertl http://www.nongnu.org/util-vserver/doc/conf/configuration.html (look for vprocunhide)
1262882293 M * pinochle do i just vprocunhid /proc/dahdi/1 ?
1262882325 J * imcsk8 ~ichavero@nat.ti.uach.mx
1262882465 M * pinochle Bertl: ok, seems like vprocunide not part of my util-vserver
1262882804 M * Bertl vprocunhide is part of any util-vserver since several years, but you do not use it like that, it is run at system startup from the runlevel scripts
1262882831 M * Bertl what you want is to change the default in that config file I pointed out to you
1262882872 M * Bertl you can test this with risk kernel module) on a host node, and  ive created the /dev/d
1262882879 M * Bertl *arg*
1262882897 M * Bertl you can test this with setattr (and the hide flag)
1262883079 M * pinochle yes, i just did that
1262883089 M * pinochle it created the /proc
1262883096 M * pinochle but does that last accross reboots?
1262883125 M * Bertl no, that's what the config file is for :)
1262883186 J * yarihm ~yarihm@80-219-169-54.dclient.hispeed.ch
1262883496 M * pinochle OH
1262883552 J * ichavero_ ~ichavero@nat.ti.uach.mx
1262883715 J * niki ~niki@188.228.10.177
1262883920 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d
1262884719 M * pinochle what exactly is a context id?
1262884852 M * Bertl the context id is the unique identifier for a context (process or network)
1262884867 M * pinochle so where do i get that number?
1262884874 M * pinochle 42 is what the example shows
1262884888 M * pinochle can two vps use the same contextid?
1262884914 M * Psy0rz_ 42 is the answer to everything
1262884964 M * pinochle :D
1262884974 M * pinochle ok, i will accept without question :D
1262885065 M * Bertl if you assign the same number to two different guests, they will share the context
1262885078 M * Bertl (note that util-vserver doesn't handle that too well atm)
1262885108 M * Bertl if you do not specify it (with recent util-vserver) the tools will choose a host unique number for you
1262885436 M * pinochle so what are the purpose behind contexts
1262885723 M * Bertl to separate environments, e.g. guests
1262885755 M * Bertl Linux-VServer is an isolation technology, i.e. processes for example, run side by side on the host, only separated by a context
1262885933 J * kolorafa ~kolorafa@dwl235.neoplus.adsl.tpnet.pl
1262885984 Q * thierryp Ping timeout: 480 seconds
1262886639 Q * kolorafa Quit: Leaving
1262886658 Q * aj__ Ping timeout: 480 seconds
1262886965 Q * jrklein Ping timeout: 480 seconds
1262887156 J * geb ~geb@earth.gebura.eu.org
1262887389 J * jrklein ~jrklein@2001:0:53aa:64c:0:44ad:b4d8:690
1262888040 J * aj__ ~aj@c192191.adsl.hansenet.de
1262888294 J * hijacker ~hijacker@87-126-142-51.btc-net.bg
1262889473 Q * niki Ping timeout: 480 seconds
1262890025 Q * barismetin Quit: Leaving...
1262893079 Q * aj__ Ping timeout: 480 seconds
1262894535 J * hijacker_ ~hijacker@87-126-142-51.btc-net.bg
1262894611 J * niki ~niki@0x5553169c.adsl.cybercity.dk
1262895038 Q * hijacker_ Quit: Leaving
1262897682 J * SubZero ~SubZero@chello089076140236.chello.pl
1262898522 J * derjohn_mob ~aj@c192191.adsl.hansenet.de
1262900939 Q * derjohn_mob Remote host closed the connection
1262901237 J * derjohn_mob ~aj@c192191.adsl.hansenet.de
1262901591 Q * bonbons Quit: Leaving
1262902934 Q * hijacker Quit: Leaving
1262904376 Q * ichavero_ Quit: This computer has gone to sleep
1262904611 Q * ghislain Quit: Leaving.
1262904702 J * docelic ~docelic@78-2-71-58.adsl.net.t-com.hr
1262906653 Q * dna Quit: Verlassend
1262906852 Q * imcsk8 Quit: Leaving
1262906985 J * thierryp ~thierry@home.parmentelat.net
1262907117 M * Mr_Smoke Bertl: ahoy :)
1262907123 M * Mr_Smoke If you're still around, that is :)
1262907132 M * Bertl yep
1262907141 M * Mr_Smoke Hooray
1262907158 M * Mr_Smoke Ok, I'm not one to bother people with the "when is the next release gonna be ready"
1262907181 M * Mr_Smoke BUT ... I'll probably need to get my hands on an updated, grsec-capable kernel soon
1262907192 M * Mr_Smoke Is this something you see happening in a near future ?
1262907233 M * Bertl there are kernels/patches for 2.6.31/32 ?
1262907250 M * Mr_Smoke That's basically what I'm after
1262907267 M * Mr_Smoke Is daniel_(noHL)_hozac the one I should bug ?
1262907343 M * Mr_Smoke Bertl: I found this > [TXT] patch-2.6.31.10-vs2.3.0.36.28-grsec2.1.14-20100107.diff 
1262907349 M * Mr_Smoke In Harry's ~
1262907351 M * Bertl http://linux-vserver.org/Welcome_to_Linux-VServer.org
1262907370 M * Mr_Smoke Dunno about its stability though
1262907374 M * Bertl scroll down, there is 2.3 + grsec
1262907391 M * Bertl for stability issues, contact harry, the non-grsec patches are supposed to be fine
1262907403 M * Mr_Smoke Yeah that's pretty much the one I found indeed
1262907410 M * Mr_Smoke Ok ... and that IPv6 thing ?
1262907415 M * Bertl (i.e. if you have any stability issues there, just contact us, and we'll fix it ASAP)
1262907430 M * Bertl yep, IPv6 is part of all vs2.3 patches
1262907444 M * Mr_Smoke Sure, but I heard there are issues left
1262907468 M * Bertl yes, there are known ipv6 issues with binding the same IP in v6 and v4
1262907492 M * Bertl but it is fine if you bind either ipv6 or ipv4
1262907508 M * Mr_Smoke Oh you mean like 1.2.3.4 and ::ffff:1.2.3.4 ?
1262907514 M * Bertl correct
1262907531 M * Mr_Smoke Does not sound like something one would want to do
1262907536 M * Mr_Smoke So it might be fine with us
1262907537 M * Mr_Smoke :)
1262907549 M * Bertl well, it sounds more likely if you consider 0.0.0.0 :)
1262907556 M * Mr_Smoke Yeah
1262907573 M * Mr_Smoke But because of the whole IP isolation business, I don't do that anymore :)
1262907582 M * Mr_Smoke Less is more :)
1262907584 M * Bertl then you should be fine
1262907672 M * Mr_Smoke Sounds good. All I need is to set up a test system
1262907677 M * Mr_Smoke Thanks for your insights :)
1262907921 Q * docelic Quit: http://www.spinlocksolutions.com/
1262908150 J * imcsk8 ~ichavero@evdomip-109-112.iusacell.net