On Wed, Sep 07, 2011 at 11:58:16AM -0400, Vivek Goyal wrote: [..] > > Not sure I understand your proposal completely in terms of > > deregistering handlers > > Actually I was thinking of using "release_agent" in a way that owner of > the group registers the release_agent. But then I realized that > release_agent seems to be per hiearchy in root group and not per cgroup. > So it is out of the window. > > So setting sticky bit for persistent group can help with the case where > libvirtd/systemd/xyz-manager does not try to remove persistent groups > created by cgconfig. But it looks like it will not handle the case of > cgconfig not removing groups shared by other services. I guess, not > removing groups which have tasks running might be an acceptable solution > but that leaves the problem that when cgroup is empty, who removes it. > A release agent again?
May be we can just come up with a default gloabl release agent "rmdir", which is installed by default by systemd for controller hierarchies. So anybody who created the groups tries to clean it up but if something is running in that group, then handler will take care of cleaning up the group later. That should be useful in handling the case of shared cgroups across cgconfig and other mangers. Thanks Vivek ------------------------------------------------------------------------------ Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ _______________________________________________ Libcg-devel mailing list Libcg-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libcg-devel
