From: Benjamin Peterson <benjamin@python.org>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org
Subject: [PATCH] cgroup_namespaces.7: wfix
Date: Thu, 16 Jul 2020 23:26:43 -0500 [thread overview]
Message-ID: <20200717042643.1013586-1-benjamin@python.org> (raw)
Signed-off-by: Benjamin Peterson <benjamin@python.org>
---
man7/cgroup_namespaces.7 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man7/cgroup_namespaces.7 b/man7/cgroup_namespaces.7
index 773379aeb..1acb82feb 100644
--- a/man7/cgroup_namespaces.7
+++ b/man7/cgroup_namespaces.7
@@ -235,7 +235,7 @@ In the absence of cgroup namespacing, because the cgroup directory
.IR /cg/1
is owned (and writable) by UID 9000 and process
.I X
-is also owned by user ID 9000, then process
+is also owned by user ID 9000, process
.I X
would be able to modify the contents of cgroups files
(i.e., change cgroup settings) not only in
--
2.25.1
next reply other threads:[~2020-07-17 4:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 4:26 Benjamin Peterson [this message]
2020-07-17 7:59 ` [PATCH] cgroup_namespaces.7: wfix Michael Kerrisk (man-pages)
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=20200717042643.1013586-1-benjamin@python.org \
--to=benjamin@python.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox