From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 218105] New: Incorrect path name in description of creating a threaded cgroups tree
Date: Sun, 05 Nov 2023 12:13:45 +0000 [thread overview]
Message-ID: <bug-218105-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218105
Bug ID: 218105
Summary: Incorrect path name in description of creating a
threaded cgroups tree
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: goeran@uddeborg.se
Regression: No
The manual page for cgroups.7 explains how to create a threaded subtree in this
way:
1. In an existing cgroup, z, that currently has the type domain, we (1)
enable one or more threaded controllers and (2) make a process a
member of z. (These two steps can be done in either order.) This
has the following consequences:
* The type of z becomes domain threaded.
* All of the descendant cgroups of x that were not already of type
threaded are converted to type domain invalid.
Where the last bullet talks about "x", it should surely talk about "z".
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2023-11-05 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 12:13 bugzilla-daemon [this message]
2023-11-11 19:57 ` [Bug 218105] Incorrect path name in description of creating a threaded cgroups tree bugzilla-daemon
2023-11-12 12:51 ` bugzilla-daemon
2024-03-04 11:50 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-218105-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.