From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 217838] Systemd nowadays mounts Cgroups v2
Date: Sat, 30 Dec 2023 05:43:37 +0000 [thread overview]
Message-ID: <bug-217838-11311-TarulCSKpK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217838-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217838
--- Comment #4 from Rajesh (r.pandian@gmail.com) ---
(In reply to Göran Uddeborg from comment #3)
> You are correct that the text is often amended by saying systemd mounts the
> v2 hierarchy on modern systems. But there is one section saying
>
> Note that on many systems, the v1 controllers are automatically
> mounted under /sys/fs/cgroup; in particular, systemd(1)
> automatically creates such mounts.
>
> In that place there is no mention that the comment only applies to older
> systems.
>
> (FYI: When I wrote the bug I was running Fedora 38, and have since upgraded
> to Fedora 39. But you can see the problem also at
> https://www.man7.org/linux/man-pages/man7/cgroups.7.html I discovered the
> issue when translating the manual page to Swedish.)
Got you. I also see the following mentioned under the section
"Cgroups v2 unified hierarchy"
"Note that on many modern systems, systemd(1) automatically mounts the cgroup2
filesystem at /sys/fs/cgroup/unified during the boot process."
May be reuse that and replace the one you have noted with the above? Does that
work?
--
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 prev parent reply other threads:[~2023-12-30 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 11:35 [Bug 217838] New: Systemd nowadays mounts Cgroups v2 bugzilla-daemon
2023-12-27 8:03 ` [Bug 217838] " bugzilla-daemon
2023-12-27 9:05 ` bugzilla-daemon
2023-12-29 21:09 ` bugzilla-daemon
2023-12-30 5:43 ` bugzilla-daemon [this message]
2023-12-30 10:01 ` 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-217838-11311-TarulCSKpK@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 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).