Quoting Victor Marmol (vmar...@google.com): > I thought we were going to use chown in the initial version to enforce the > ownership/permissions on the hierarchy. Only the cgroup manager has access > to the hierarchy, but it tries to access the hierarchy as the user that > sent the request. It was only meant to be a "for now" solution while the > real one rolls out. It may also have gotten thrown out since last I heard :)
Actually that part wasn't meant as a "for now" solution. It can of course be thrown away in favor of having the daemon store all this information, but I'm seeing no advantages to that right now. There are other things which the daemon can eventually try to keep track of, if we don't decide they belong in a higher layer. -serge ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ lxc-devel mailing list lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
