Recent changes to feature-requests

NOT (!) operator in cgrules.conf?

Joseph Santaniello — Wed, 09 Jul 2014 13:02:39 -0000

I have a scenario where it would be very helpful for cgrulesengd to recognize the ! operator. An example cgrules.conf:

user:!command * group/

Which would cause all of user's tasks EXCEPT "command" to be classified into "group"

Thanks!

ID-Range for cgrulesengd

Anonymous — Mon, 08 Nov 2010 10:08:43 -0000

Hi all,
I'm in a project, where the system should be secured from wired user applications, all user accounts are stored in LDAP so we'd like to configure cgrulesengd to move an ID range f.e. 10000-25000 to one cgroup.
ATM I'm using a collector script, which is started via cronjob, but this is only a dirty workaround for the problem.
Would be nice to see this improvement in a patch or in upcoming version.

double loading the same config unloads the earlier one

Sudhir Kumar — Mon, 10 Nov 2008 13:21:51 -0000

Hi
Loading the same file agian should not clean earlier mounted controllers. However the current parser unloads the existing setup.

[root@e325b my-configs]# cgconfigparser -l basic.conf
[root@e325b my-configs]# pm
cgroup /container cgroup rw,cpu 0 0
cgroup /memory cgroup rw,memory 0 0
[root@e325b my-configs]# cgconfigparser -l basic.conf
Loading configuration file basic.conf failed, error: Device or resource busy
return code = 50021
[root@e325b my-configs]# pm
[root@e325b my-configs]#

Here pm is cat /proc/mounts | grep -w cgroup

However this needs a discussion but anyway this is an unexpected behaviour.

Thanks
sudhir