Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

cgrules.conf(5) [debian man page]

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 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. 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. 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)

Check Out this Related Man Page

CGCONFIGPARSER(8)						 libcgroup Manual						 CGCONFIGPARSER(8)

NAME
cgconfigparser - setup control group file system SYNOPSIS
cgconfigparser [-h] [-l <filename>] [-L <directory>] [...] OPTIONS
-h, --help Displays help. -l, --load=FILE Parses the control groups configuration file Sets up the control group file system defined by the configuration file and mounts mount points defined by the configuration file. The format of the file is described in cgconfig.conf. This option can be used mul- tiple times and can be mixed with -L option. -L, --load-directory=DIR Finds all files in given directory and parses them in alphabetical order like they were specified by -l option. This option can be used multiple times and can be mixed with -l option. -a <agid>:<auid> defines the default owner of 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 default permissions of a control groups directory. The permissions needs to be specified as octal numbers e.g. -d 775. -f, --fperm=mode sets the default permissions of the control group files. 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). -s, --tperm=mode sets the default permissions of the control group tasks files. 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 per- missions to the owners permissions). -t <tuid>:<tgid> defines the default owner of tasks file of the defined control group. I.e. this user and members of this group have write access to the file. SEE ALSO
cgconfig.conf (5) Linux 2009-03-16 CGCONFIGPARSER(8)
Man Page

Featured Tech Videos