Re: [lxc-devel] [RFC] [PATCH 0/6] Major cgroup logic rewrite

2013-09-10 Thread Serge Hallyn
Quoting Christian Seiler (christ...@iwakd.de): > Hi Serge, > > > Thanks, Christian. I did need the trivial white-space-damaged patch below, > > but > > with that it built and ran for me, both with %n and default (/lxc/%n) > > patterns. > > This was in a nested container, I haven't tested at hos

Re: [lxc-devel] [RFC] [PATCH 0/6] Major cgroup logic rewrite

2013-09-09 Thread Serge Hallyn
Quoting Christian Seiler (christ...@iwakd.de): > Hi Serge, > > > Thanks, Christian. I did need the trivial white-space-damaged patch below, > > but > > with that it built and ran for me, both with %n and default (/lxc/%n) > > patterns. > > This was in a nested container, I haven't tested at hos

Re: [lxc-devel] [RFC] [PATCH 0/6] Major cgroup logic rewrite

2013-09-09 Thread Serge Hallyn
Quoting Serge Hallyn (serge.hal...@ubuntu.com): > Quoting Christian Seiler (christ...@iwakd.de): > > Hi Serge, > > > > > Thanks, Christian. I did need the trivial white-space-damaged patch > > > below, but > > > with that it built and ran for me, both with %n and default (/lxc/%n) > > > pattern

Re: [lxc-devel] [RFC] [PATCH 0/6] Major cgroup logic rewrite

2013-09-09 Thread Serge Hallyn
Quoting Christian Seiler (christ...@iwakd.de): > Hi all, > > As discussed previously, I've now done a major rewrite of the entire > cgroup logic. There are now no assumptions made whatsoever when it > comes to the cgroup mount points, the kernel information will be used > to determine the proper l

Re: [lxc-devel] [RFC] [PATCH 0/6] Major cgroup logic rewrite

2013-09-09 Thread Christian Seiler
Hi Serge, > Thanks, Christian. I did need the trivial white-space-damaged patch below, > but > with that it built and ran for me, both with %n and default (/lxc/%n) > patterns. > This was in a nested container, I haven't tested at host level but have no > reason to think that would fail if nest

[lxc-devel] [RFC] [PATCH 0/6] Major cgroup logic rewrite

2013-09-08 Thread Christian Seiler
Hi all, As discussed previously, I've now done a major rewrite of the entire cgroup logic. There are now no assumptions made whatsoever when it comes to the cgroup mount points, the kernel information will be used to determine the proper locations for everything. (Only /proc is assumed to be worki