< Features
(Initial revision) |
|||
| Line 4: | Line 4: | ||
Our goals are to improve the existing tools where necessary and feasible and/or to create new ones e.g. to create or modify persistent cgroups configuration. At the beginning the focus will be on command line tools, but we'll keep in mind that in the long term we'll likely want to have graphical tools. These would offer similar functionality and we should try to make sure that any non-UI code written is usable from both kinds of frontends. | Our goals are to improve the existing tools where necessary and feasible and/or to create new ones e.g. to create or modify persistent cgroups configuration. At the beginning the focus will be on command line tools, but we'll keep in mind that in the long term we'll likely want to have graphical tools. These would offer similar functionality and we should try to make sure that any non-UI code written is usable from both kinds of frontends. | ||
varekova: for now I'm trying to create a /etc/cgconfig.conf file which could be parsed by cgconfig service but I'm unsuccessful for now - I use the example one (which is in the package, but it does not works - I'm not sure whether there should be some other stuff which have to be done before this service is started) | |||
Revision as of 15:10, 18 December 2008
Control Groups
Since kernel 2.6.24, Linux has so called control groups as a means to partition available resources between running processes. Libcgroups makes that functionality available to programmers and contains two tools, cgexec and cgclassify, to start processes in a control group or move existing processes from one control group to another.
Our goals are to improve the existing tools where necessary and feasible and/or to create new ones e.g. to create or modify persistent cgroups configuration. At the beginning the focus will be on command line tools, but we'll keep in mind that in the long term we'll likely want to have graphical tools. These would offer similar functionality and we should try to make sure that any non-UI code written is usable from both kinds of frontends.
varekova: for now I'm trying to create a /etc/cgconfig.conf file which could be parsed by cgconfig service but I'm unsuccessful for now - I use the example one (which is in the package, but it does not works - I'm not sure whether there should be some other stuff which have to be done before this service is started)