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.
Bug 682002 - documentation error in doc-resource-management guide
Summary: documentation error in doc-resource-management guide
Keywords:
Status: CLOSED DUPLICATE of bug 667623
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Resource_Management_Guide
Version: 6.0
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Martin Prpič
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-03 20:50 UTC by steve
Modified: 2011-03-07 08:28 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-07 08:28:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description steve 2011-03-03 20:50:45 UTC
Section 2.1.1 contains

********begin doc sample ****************

mount {
    cpuset = /cgroup/cpuset;
}

creates a hierarchy for the cpuset subsystem, the equivalent of the shell commands:

        mkdir /cgroup/cpuset
        mount -t cgroup -o cpuset cpuset /cgroup/cpuset

Group entries create control groups and set subsystem parameters. For example: 

group daemons/sql {
    perm {
        task {
            uid = root;
            gid = sqladmin;
        } admin {
            uid = root;
            gid = root;
        }
    } cpuset {
        cpuset.cpus = 0-3;
    }
}

creates a control group for sql daemons, with permissions for users in the sqladmin group to add tasks to the control group and the root user to modify subsystem parameters. When combined with the example of the mount entry above, the equivalent shell commands are:

mkdir -p /cgroup/cpu/daemons/sql
chown root:root /cgroup/cpu/daemons/sql/*
chown root:sqladmin /cgroup/cpu/daemons/sql/tasks
echo 0-3 > /cgroup/cpu/daemons/sql/cpuset.cpus

*********end doc sample **************


   The 4 shell commands are incorrect for the example above. They should
be

mkdir -p /cgroup/cpuset/daemons/sql
chown root:root /cgroup/cpuset/daemons/sql/*
chown root:sqladmin /cgroup/cpuset/daemons/sql/tasks
echo 0-3 > /cgroup/cpuset/daemons/sql/cpuset.cpus

  ie replace directory "cpu" with "cpuset". I think.

Comment 2 Martin Prpič 2011-03-07 08:28:59 UTC
Hey Steve, this bug is similar to BZ#667623, the issue has been fixed. Correct version will be available in the next release. Thank you for reporting this issue!

Martin

*** This bug has been marked as a duplicate of bug 667623 ***


Note You need to log in before you can comment on or make changes to this bug.