As I was trying to understand this system, I was initially very confused by the separation between libcgroup and the included tools that use the library. For example, cgconfig.conf describes itself as the "libcgroup configuration file", but isn't it actually just the configuration file for cgconfigparser?
I think it'd make a lot of sense to split the library from the tools. In some ways this is a packaging issue, but it runs through the way the documentation talks about everything as well. Further, I'd suggest splitting the "static" command-line utilities like cgreate and cgexec from the policy-effecting cgred. I think that's a little less important, but some people may want access to the convenient utilities without necessarily having the policy daemon running. So, I'm going to suggest making sub-packages on the Fedora side which match the sub-trees in your source package: libcgroup libcgroup-tools libcgroup-daemon libcgroup-pam if everyone thinks that makes sense. Also, if a developer could go through the documentation and try and make the distinction between library and tools more clear, I think it'd be helpful. Thanks! -- Matthew Miller [email protected] <http://mattdm.org/> ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Libcg-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libcg-devel
