SUSE Support

Here When You Need Us

Converting deprecated libcgroup configurations

This document (7023842) is provided subject to the disclaimer at the end of this document.


SUSE Linux Enterprise Server 12 Service Pack 4 (SLES 12 SP4)


In SLES 12 SP3 libcgroup has been deprecated. In SLES 12 SP4 the libcgroup1 and libgroup-tools packages have been removed. This TID gives assistance for moving to a non-libcgroup setup.3.1) Using controllers not handled by systemd


1) What controllers are used (cgconfig.conf)?

## cpuset
Systemd does not handle cpuset controller.

Similar effect on scheduling can be achieved by calling sched_setaffinity(2) and set_mempolicy(2) directly from a restricted program.

systemd provides CPUAffinity= directive that uses sched_setaffinity(2), there is no counterpart for set_mempolicy(2) though.

If the suggestions above does not cover the use case, see 3.1) below.

## cpu
CPUShares=, CPUQuota=
(see `man systemd.resource-control`)

NOTE: Realtime group scheduling attributes of the controller are not supported by systemd.

## cpuacct
(see `man systemd.resource-control`)

## memory
(see `man systemd.resource-control`)

## devices
DevicePolicy=, DeviceAllow=

(see `man systemd.resource-control`)
## freezer
Manual use.

## net_cls
(see `man systemd.resource-control`)

## blkioBlockIOWeight=, BlockIODeviceWeight=, BlockIOReadBandwidth=
(see `man systemd.resource-control`)

2) What are the hierarchies (cgconfig.conf)?

If the controller is handled by systemd, the hierarchy tree is built from slice units (inner nodes) and service or scope units (leaves).

If the controller is not handled by systemd, the hierarchy must be created and configured manually.

mkdir -p /sys/fs/cgroup/$CONTROLLER/path/to/cgroup
echo $VALUE >/sys/fs/cgroup/$CONTROLLER/path/to/cgroup/$ATTRIBUTE

There is an unsupported helper Python script that parses configuration in libcgroup format and creates the hierarchy with attributes set. It can be requested from support as needed.

3) What processes are classified (cgrules.conf)?

NOTE: Asynchronous classification as performed by cgrulesengd is unreliable and proper way to classify processes is to fork(2) a new one, attach it to a cgroup and then exec(2) the to-be-classified program.

If the process to classify is a daemon, then configure proper directives of a respective systemd service (`man systemd.resource-control`).

If the process to classify is a one-time task, then a systemd-run can be used to realize the fork(2)-classify-exec(2) idiom.

systemd-run --scope --slice=restricted.slice $PROGRAM
systemd-run --scope -p MemoryLimit=256M $PROGRAM

NOTE: systemd-run can only be run by privileged user.

3.1) Using controllers not handled by systemd

This applies to cpuset particularly and relies on cset utility. It can be used as a wrapper and can be composed with other commands (when run as privileged
systemd-run --scope --slice=restricted.slice cset proc --exec $CGROUP $PROGRAM

ExecStart=/usr/bin/cset proc --exec $CGROUP $DAEMON

3.1.1) Classifying processes of unprivileged users

The permissions in the particular controller hierarchy allow only privileged users to modify it. Hence the process must be classified before dropping privileges.
cset proc --exec $CGROUP \
  systemd-run --scope --uid=$T_UID --slice=restricted.slice $PROGRAM
systemd-run --scope --slice=restricted.slice \
  cset proc -u $T_UID --exec $CGROUP $PROGRAM

ExecStart=/usr/bin/cset proc -u $T_UID --exec $CGROUP $PROGRAM

NOTE: It is not possible User= directive of service files because UID change would happen before cset is executed.

3.1.2) Implicit classification

Implicit classification is yielded by wildcard rule at the end of cgrules.conf
    *    cpuset    target/cgroup

Such a rule typically serves to divert all system tasks away from root cpuset on partitioned system. For that please see the chapter about shielding using cset (

NOTE: Similar behavior can be achieved with isolcpus= kernel command line. This has two major drawbacks: a) any process can do sched_setaffinity(2) to an isolated CPU, b) there is no load balancing among isolated CPUs. Hence it is discouraged.


Additional Information


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7023842
  • Creation Date: 30-Apr-2019
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.