1415578901 Q * Ghislain Quit: Leaving.
1415581201 Q * fstd Remote host closed the connection
1415581252 J * fstd ~fstd@xdsl-81-173-190-124.netcologne.de
1415604477 J * Ghislain ~aqueos@adsl1.aqueos.com
1415604706 Q * ___nlm___ Quit: leaving
1415605404 N * Bertl_zZ Bertl
1415605406 M * Bertl morning folks!
1415605799 Q * Ghislain Ping timeout: 480 seconds
1415606686 J * Ghislain ~aqueos@adsl2.aqueos.com
1415607827 Q * geos_one Quit: ChatZilla 0.9.91 [Firefox 33.0/20141016201439]
1415608259 Q * thierryp Remote host closed the connection
1415608272 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:71ca:d04:d319:b50a
1415609857 M * Ghislain hello
1415609952 M * Ghislain when you set a vdu usage for a directory wxhere no limits have been specified with vdlimit -s ...
1415609977 M * Ghislain this will enforce this saying there is a quota of 0 therefor forbidding any operation ?
1415610116 M * Bertl yes, you shouldn't be able to create anything there which consumes space
1415610129 M * Bertl you can still overwrite stuff and/or remove files I guess
1415610150 M * Ghislain ok
1415610207 M * Ghislain thanks my install script was recording the size before setting the limit therefor everything  went to the rabit hole :) 
1415621883 J * FireEgl ~FireEgl@173-23-76-11.client.mchsi.com
1415622389 N * Bertl Bertl_oO
1415624401 Q * fstd Remote host closed the connection
1415624417 J * fstd ~fstd@xdsl-84-44-225-12.netcologne.de
1415626251 M * Ghislain is there a way to give rw access to a sub directory of /dev in a guest ? i mount it in the guest fine but then it cannot wrtite to it
1415626586 M * Ghislain i guess this will be too dangerous
1415627027 M * Ghislain dam nfs server in userland do not exist anymore
1415628072 M * Ghislain well vprocunhide if i unhide /proc/fs i still do not see it in the guest
1415628303 M * Ghislain ohh
1415628326 M * Ghislain got it i need to unhide /proc/fs and /proc/fs/nfsd, does it accept wilcards ?
1415631278 J * Wermwud ~Wermwud@69-29-150-18.stat.centurytel.net
1415633862 M * CcxCZ Ghislain: iirc there should be no issue with /dev being rw, the guest just can't make device nodes by default
1415634812 J * BenG ~bengreen@bmex-gw.bristolwireless.net
1415636523 M * Ghislain yes but nfsd allways stop on something even with sys_admin and net_admin on
1415636665 M * Ghislain CcxCZ:  last error i was able to reach was Starting NFS kernel daemon: nfsdrpc.nfsd: writing fd to kernel failed: errno 111
1415636717 M * CcxCZ I'm not sure if it's possible to run the in-kernel nfs server from within vserver
1415636728 M * CcxCZ I never managed to at least
1415636735 M * Ghislain CcxCZ: : it wxas populatin /dev/fs/nfsd with all the needed files but then failed. Historicaly it was not
1415636776 M * Ghislain but i try from time to time to see if i can get it even with loosing all security at least i will keep my host/guest speparation for management purppose
1415636801 M * Ghislain putting things in the host is a real pain for me
1415636891 M * CcxCZ yeah. that's the pain of it being in-kernel and not a proper daemon
1415636936 M * CcxCZ welp, better ask someone who actually digs in the kernel for advice, can't help you there much
1415637174 M * Ghislain humm
1415637217 M * Ghislain well i tried again and it seems to work now..weird, let me test a client and get back to you ( of course with all those cap the security level is 0...)
1415637236 M * ard what?
1415637248 M * ard nfs-kernel-server from linux-vserver?
1415637250 M * ard how?
1415637261 M * ard and with network namespaces or contexts?
1415637345 M * Ghislain let me test and if i get somethign working i will put a wiki page with what i done, not not any network namespace but with a LOT of ccap given to the guest. not sure yet if this works, need to test
1415637453 M * CcxCZ might be easier to run nfs from plain chroot than hassle with vserver sice I suspect you'd have to disable most of the security anyway
1415637677 M * Ghislain yes but that way you keep the setup you use everywhere else, the security is not usable here but all the other system can use the same template and mecanism from support to monitoring to upgrades etc...
1415638403 M * CcxCZ well, vserver is pretty much just chroot if you remove all the security/isolation
1415638595 M * Ghislain that is not a security question but management question. Creating one exception make you change everything from support to monitoring to backlups etc
1415638628 M * Ghislain if you manage 4 servers no issues, but you cannot make a living managing 4 machien so i need to standardise the most of it
1415639143 Q * BenG Quit: I Leave
1415639294 J * bonbons ~bonbons@2001:a18:201:5a01:2d05:cbec:f0d5:dd8e
1415645560 J * zerick ~eocrospom@190.117.185.146
1415648352 Q * thierryp Remote host closed the connection
1415649777 J * thierryp ~thierry@home.parmentelat.net
1415650221 M * Bertl_oO off for a nap ... bbl
1415650222 N * Bertl_oO Bertl_zZ
1415653517 Q * thierryp Remote host closed the connection
1415653559 Q * yoshi314_ Ping timeout: 480 seconds
1415653914 J * yoshi314_ ~yoshi314@sundance.vichan.net
1415654414 Q * Aiken Ping timeout: 480 seconds
1415655508 J * thierryp ~thierry@home.parmentelat.net
1415655734 J * Aiken ~Aiken@d63f.h.jbmb.net
1415655993 Q * thierryp Ping timeout: 480 seconds
1415656014 J * kshannon_ ~kris@server.kris.shannon.id.au
1415656073 Q * kshannon Read error: Connection reset by peer
1415656281 J * thierryp ~thierry@home.parmentelat.net
1415656762 Q * thierryp Ping timeout: 480 seconds
1415657130 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:35a3:2e99:5ba2:d113
1415657208 Q * bonbons Quit: Leaving
1415658737 N * Bertl_zZ Bertl
1415658740 M * Bertl back now ...
1415661226 M * hlew Hello, does anyone have any tips on working with/configuring the OOM killer to be context aware?
1415661568 Q * CcxCZ Ping timeout: 480 seconds
1415661762 J * CcxCZ ~ccxCZ@asterix.te2000.cz
1415662294 M * Bertl hey hlew!
1415662301 M * hlew Hi.
1415662307 M * Bertl in a recent kernel, the cgroups are used to limit memory
1415662325 M * hlew Yes, I did see this.
1415662326 M * Bertl and thus, the OOM killer should be limited to the cgroups
1415662348 M * Bertl (given that the cgroup is configured properly)
1415662355 M * hlew So the OOM killer kills based on the limits I set in memory.limit_in_bytes and memory.memsw?
1415662374 M * hlew Err, memory.memsw_limit_in_bytes.
1415662505 M * hlew I was just concerned because I saw some behavior which made me suspect that the OOM killer was killing processes in other contexts.
1415662976 M * Bertl it should do that, if not, then it is a mainline bug and should be reported to the cgroup folks
1415663115 M * hlew Alright, thanks for the insight. It may have more to do with the specifics of the system because the Ubuntu kernel I'm using has lowmemorykiller.c (from Android kernel staging) compiled into it.
1415663148 M * Bertl yeah, that might affect it somehow
1415663486 Q * zerick Ping timeout: 480 seconds