Your message dated Wed, 31 Mar 2021 22:20:32 +0200 with message-id <d7875931-713a-1436-56e0-264408e20ab0@debian.org> and subject line Re: Bug#985446: release-notes: cgroupv2 is the default cgroup hierarchy has caused the Debian Bug report #985446, regarding release-notes: cgroupv2 is the default cgroup hierarchy to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 985446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985446 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: release-notes: cgroupv2 is the default cgroup hierarchy
- From: Michael Biebl <biebl@debian.org>
- Date: Thu, 18 Mar 2021 12:35:48 +0100
- Message-id: <[🔎] 161606734818.3605.13665126551169839649.reportbug@pluto.milchstrasse.xx>
Package: release-notes Severity: normal X-Debbugs-Cc: pkg-systemd-maintainers@lists.alioth.debian.org Starting with bullseye, the default cgroup hierarchy will be unified, ie. cgroupv2 only. We have this section in our systemd.NEWS file: systemd (247.2-2) unstable; urgency=medium systemd now defaults to the "unified" cgroup hierarchy (i.e. cgroupv2). This change reflects the fact that cgroups2 support has matured substantially in both systemd and in the kernel. All major container tools nowadays should support cgroupv2. If you run into problems with cgroupv2, you can switch back to the previous, hybrid setup by adding "systemd.unified_cgroup_hierarchy=false" to the kernel command line. You can read more about the benefits of cgroupv2 at https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html -- Michael Biebl <biebl@debian.org> Mon, 21 Dec 2020 18:40:10 +0100 We should add something similar to the release notes. The above text could be a good starting point. We track issues related to cgroupv2 via user tags [1]. Some tools, most notably probably is libcgroup [2], don't support cgroupv2 yet. Regards, Michael [1] https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-systemd-maintainers@lists.alioth.debian.org;tag=cgroupv2 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959022
--- End Message ---
--- Begin Message ---
- To: Michael Biebl <biebl@debian.org>, 985446-done@bugs.debian.org
- Subject: Re: Bug#985446: release-notes: cgroupv2 is the default cgroup hierarchy
- From: Paul Gevers <elbrus@debian.org>
- Date: Wed, 31 Mar 2021 22:20:32 +0200
- Message-id: <d7875931-713a-1436-56e0-264408e20ab0@debian.org>
- In-reply-to: <[🔎] 161606734818.3605.13665126551169839649.reportbug@pluto.milchstrasse.xx>
- References: <[🔎] 161606734818.3605.13665126551169839649.reportbug@pluto.milchstrasse.xx>
Hi, On 18-03-2021 12:35, Michael Biebl wrote: > Starting with bullseye, the default cgroup hierarchy will be unified, > ie. cgroupv2 only. I pushed the last proposal in the MR from zigo. PaulAttachment: OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---