> > No, as Lennart stated earlier in this thread, systemd is limited to > create only simple hierarchies, for complex ones cgconfig should be used > to create and configure groups for services. So systemd and cgconfig > should cooperate in shared cgroup trees, they won't have separate subtrees. >
Oh! and I was using the following as context "Lennart just informed me that systemd can now handle mounting different hierarchies as required by the user (as opposed to a preconfigured systemd default). With this in mind, I propose to make cgconfig a lot simpler. Once an official release of systemd is tagged, we are going to go forward and make cgconfig only handle namespaces and pre-created groups. At some point the future we should also figure out how to deprecate cgrulesengd and then we are just remaining with the core of the library which is soon going to go through a complete rewrite. Comments/Objections are welcome." Balbir Singh ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Libcg-devel mailing list Libcg-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libcg-devel
