From: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] cgroups.7: tfix
Date: Sat, 8 Oct 2016 15:58:36 +0200 [thread overview]
Message-ID: <20161008135836.3977-1-jwilk@jwilk.net> (raw)
Signed-off-by: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
---
man7/cgroups.7 | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/man7/cgroups.7 b/man7/cgroups.7
index 9dc0e15..556dea6 100644
--- a/man7/cgroups.7
+++ b/man7/cgroups.7
@@ -28,7 +28,7 @@
cgroups \- Linux control groups
.SH DESCRIPTION
Control cgroups, usually referred to as cgroups,
-are a Linux kernel feature which which allow processes to
+are a Linux kernel feature which allow processes to
be organized into hierarchical groups whose usage of
various types of resources can then be limited and monitored.
The kernel's cgroup interface is provided through
@@ -453,7 +453,7 @@ under both the v1 and the v2 hierarchies.
The new behaviors in cgroups v2 are summarized here,
and in some cases elaborated in the following subsections.
.IP 1. 3
-Cgroups v2 provides a unified hiearchy against
+Cgroups v2 provides a unified hierarchy against
which all controllers are mounted.
.IP 2.
"Internal" processes are not permitted.
@@ -593,7 +593,7 @@ since a single process can monitor multiple
files.
By contrast, the cgroups v1 mechanism requires the creation
of a process for each notification.
-Second, notfication can be delegated to a process that lives inside
+Second, notification can be delegated to a process that lives inside
a container associated with the newly empty cgroup.
.\"
.SS /proc files
--
2.9.3
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-10-08 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 13:58 Jakub Wilk [this message]
[not found] ` <20161008135836.3977-1-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2016-10-08 18:08 ` [PATCH] cgroups.7: tfix Michael Kerrisk (man-pages)
2018-01-02 22:55 Jakub Wilk
[not found] ` <20180102225532.894-1-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2018-01-03 0:40 ` Michael Kerrisk (man-pages)
2018-01-26 13:40 Jakub Wilk
[not found] ` <20180126134026.2960-1-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2018-01-26 18:59 ` Michael Kerrisk (man-pages)
2019-08-24 21:11 Eric Biggers
2019-08-26 21:06 ` 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=20161008135836.3977-1-jwilk@jwilk.net \
--to=jwilk-txgolizoknreowh0uzbu5w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).