cgcreate(1) [debian man page]

CGCREATE(1)							 libcgroup Manual						       CGCREATE(1)

NAME

       cgcreate - create new cgroup(s)

SYNOPSIS

       cgcreate [-h] [-s] [-t <tuid>:<tgid>] [-a <agid>:<auid>] [-f mode] [-d mode] -g <controllers>:<path> [-g ...]

DESCRIPTION

       The command creates new cgroup(s) defined by the options -g.

       -a <agid>:<auid>
	      defines  the  name of the user and the group which own the rest of the defined control group's files. These users are allowed to set
	      subsystem parameters and create subgroups.  The default value is the same as has the parent cgroup.

       -d, --dperm=mode
	      sets the permissions of a control groups directory.  The permissions needs to be specified as octal numbers e.g.	-d 775.

       -f, --fperm=mode
	      sets the permissions of the control groups parameters.  The permissions needs to be specified as octal numbers e.g.   -f	775.   The
	      value  is  not  used as given because the current owner's permissions are used as an umask (so 777 will set group and others permis-
	      sions to the owners permissions).

       -g <controllers>:<path>
	      defines control groups to be added.  controllers is a list of controllers and path is the relative path to  control  groups  in  the
	      given controllers list. This option can be specified multiple times.

       -h, --help
	      display this help and exit

       -s, --tperm=mode
	      sets  the  permissions  of  the control group tasks file.  The permissions needs to be specified as octal numbers e.g.  -f 775.  The
	      value is not used as given because the current owner's permissions are used as an umask (so 777 will set group  and  others  permis-
	      sions to the owners permissions).

       -t <tuid>:<tgid>
	      defines  the  name of the user and the group, which owns tasks file of the defined control group. I.e. this user and members of this
	      group have write access to the file.  The default value is the same as has the parent cgroup.

FILES

SEE ALSO

       cgrules.conf (5) cgexec (1) cgclassify (1)

Linux								    2009-03-15							       CGCREATE(1)

CGRULES.CONF(5) 						 libcgroup Manual						   CGRULES.CONF(5)

NAME

       cgrules.conf - libcgroup configuration file

DESCRIPTION

       cgrules.conf configuration file is used by libcgroups to define control groups to which a process belongs.

       The file contains a list of rules which assign to a defined group/user a control group in a subsystem (or control groups in subsystems).

       Rules have two formats:

	   <user>		    <controllers>	<destination>
	   <user>:<process name>    <controllers>	<destination>

       Where:

       user can be:
	   - a user name
	   - a group name with @group syntax
	   - the wildcard '*', for any user or group
	   - '%', which is equivalent to "ditto" (useful for
	     multi-line rules where different cgroups need to be
	     specified for various hierarchies for a single user)

       process name is optional and it can be:
	   - a process name
	   - a full command path of a process

       controllers can be:
	   - comma separated controller names (no spaces) or
	   - * (for all mounted controllers)

       destination can be:
	   - path relative to the controller hierarchy (ex. pgrp1/gid1/uid1)
	   - following strings called "templates" and will get expanded

		 %u	username, uid if name resolving fails
		 %U	uid
		 %g	group name, gid if name resolving fails
		 %G	gid
		 %p	process name, pid if name not available
		 %P	pid

		 '' can be used to escape '%'
       First rule which matches the criteria will be executed.

       Any text starting with '#' is considered as a start of comment line and is ignored.

       If  the	destination contains template string, the control group can be created on-fly. In time when some process wants to use the template
       rule which leads to control group (see cgexec (1)) and the control group does not exist, the group is created. The template  control  group
       parameters  can	be  specified in cgconfig.conf configuration file. See (cgconfig.conf (5)).  If the template definition is not found there
       created group have default kernel setting.

EXAMPLES

       student	       devices	       /usergroup/students
       Student's processes in the 'devices' subsystem belong to the control group /usergroup/students.

       student:cp	devices 	/usergroup/students/cp
       When student executes 'cp' command, the processes in the 'devices' subsystem belong to the control group /usergroup/students/cp.

       @admin		*	       admingroup/
       Processes started by anybody from admin group no matter in what subsystem belong to the control group admingroup/.

       peter	       cpu	       test1/
       %	       memory	       test2/
       The first line says Peter's task for cpu controller belongs to test1 control group. The second one says Peter's tasks for memory controller
       belong to test2/ control group.

       *	       *	       default/
       All  processes  in  any	subsystem belong to the control group default/. Since the earliest matched rule is applied, it makes sense to have
       this line at the end of the list. It will put a task which was not mentioned in the previous rules to default/ control group.

       @students cpu,cpuacct	students/%u
       Processes in cpu and cpuacct subsystems started by anybody from students group belong to group students/name. Where "name" is user name	of
       owner of the process.

FILES

       /etc/cgrules.conf
       default libcgroup configuration file

SEE ALSO

       cgconfig.conf (5), cgclassify (1), cgred.conf (5)

BUGS

Linux								    2009-03-10							   CGRULES.CONF(5)