Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
I've tried the example in chapter 2.1.1 of Resource Management Guide, Edition 1.0 and both the cgconfig.conf sample and sequence of shell commands are wrong.
cgconfig.conf problem:
You create two groups: daemons and daemons/sql. The daemons/sql is created explicitly as written in the config file. But the cgconfig service must create also daemons group - on the pseudofilesystem, 'sql' is just subdirectory of 'daemons', so 'daemons' must be created. Since the daemons group does not have set any cpuset.cpus, it is *not* possible to set cpuset.cpus in daemons/sql (because cpuset.cpus in daemons/sql must be subset of parent's cpuset.cpus and it is not set). Maybe cpuset controller is bad example, you won't get into this troubles if you use cpu controller instead (and cpu.shares as parameter - it's always set by kernel when a new group is created, unlike cpuset.cpus).
shell sequence problem:
You mount cpuset to /cgroup/cpuset, but one paragraph below you use 'mkdir -p /cgroup/cpu/daemons/sql'. It should be/cgroup/*cpuset*/daemons/sql.
And the same problem as above arises, you mkdir -p /cgroup/cpu/daemons/sql, which creates 'daemons' group, but you don't set its cpuset.cpus, so you can't set it in any of its subgroups, 'echo 0 > /$TMP/cgroup/cpuset/daemons/sql/cpuset.cpus' fails with echo: write error: Permission denied,