3
#Each line describes a rule for a user in the forms:
5
#<user> <controllers> <destination>
6
#<user>:<process name> <controllers> <destination>
11
# - a group name, with @group syntax
12
# - the wildcard *, for any user or group.
13
# - The %, which is equivalent to "ditto". This is useful for
14
# multiline rules where different cgroups need to be specified
15
# for various hierarchies for a single user.
17
# <process name> is optional and it can be:
19
# - a full command path of a process
21
# <controller> can be:
22
# - comma separated controller names (no spaces)
23
# - * (for all mounted controllers)
25
# <destination> can be:
26
# - path with-in the controller hierarchy (ex. pgrp1/gid1/uid1)
29
# - It currently has rules based on uids, gids and process name.
31
# - Don't put overlapping rules. First rule which matches the criteria
34
# - Multiline rules can be specified for specifying different cgroups
35
# for multiple hierarchies. In the example below, user "peter" has
36
# specified 2 line rule. First line says put peter's task in test1/
37
# dir for "cpu" controller and second line says put peter's tasks in
38
# test2/ dir for memory controller. Make a note of "%" sign in second line.
39
# This is an indication that it is continuation of previous rule.
42
#<user> <controllers> <destination>
44
#john cpu usergroup/faculty/john/
45
#john:cp cpu usergroup/faculty/john/cp
46
#@student cpu,memory usergroup/student/
added
removed
samples/cgrules.conf
