On Tue, Aug 23, 2011 at 09:17:32PM +0200, Lennart Poettering wrote: > On Tue, 23.08.11 11:20, Dhaval Giani (dhaval.gi...@gmail.com) wrote: > > > > It is a relatively lose model. If that's the goal, then things are > > > fine. But I don't think that's the goal you had started with. > > > > Actually the original plan was this itself. The persistent stuff is > > stored by cgconfig, and the non persistent stuff can be created on the > > fly. We can always treat systemd as non-persistent and not bother > > about it. > > Yupp, that's how I like to see it. > > In fact, the sticky bit thing is probably what should be used to > distuingish persistant and volatile cgroups. libvrit and systemd should > create their groups without that bit, and delete their groups if the bit > is not set. cgconfig should set the bit to tell systemd/libvirt that a > specific cgroups should be considered persistant and not be deleted by > systemd/libvirtd.
Or the subsystem who is responsible for creating cgroup should be responsible for deleting it (if need be). So if libvirt and systemd can check for presence of group and register removal handler only if group was freshly created, that should help too? Thanks Vivek ------------------------------------------------------------------------------ EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev _______________________________________________ Libcg-devel mailing list Libcg-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libcg-devel
