diff options
author | Florian Schmaus <flow@gentoo.org> | 2023-06-14 17:20:13 +0200 |
---|---|---|
committer | Sam James <sam@gentoo.org> | 2023-07-29 12:24:45 +0100 |
commit | f8e3b11496bd6d602a690535c4a3bb32bb8e9744 (patch) | |
tree | 739fc45d7de986291c22a91885285bb5e8cdc3c0 /man | |
parent | dbapi: add some typing (diff) | |
download | portage-f8e3b11496bd6d602a690535c4a3bb32bb8e9744.tar.gz portage-f8e3b11496bd6d602a690535c4a3bb32bb8e9744.tar.bz2 portage-f8e3b11496bd6d602a690535c4a3bb32bb8e9744.zip |
Drop FEATURES=cgroup, i.e., v1 cgroup usage
Remove portage's usage of Linux version 1 cgroups, which are itself
superseded by version 2 cgroups. This basically reverts
b01a1b90d8c5 ("Add FEATURES=cgroup to isolate phase processes.").
Portage's usage of version 1 cgroups has caused some issues in the
past. For example https://bugs.gentoo.org/894398, where LXD got
confused by the existence of the version 1 cgroup created by portage.
Arguably, this could be considered a bug in LXD, but with
FEATURES=pid-sandbox, as better alternative to FEATURES=cgroup
exists. And removing the code for FEATURES=cgroup reduces portage's
code size, which is also a plus.
Bug: https://bugs.gentoo.org/894398
Signed-off-by: Florian Schmaus <flow@gentoo.org>
Reviewed-by: Michał Górny <mgorny@gentoo.org>
Closes: https://github.com/gentoo/portage/pull/1057
Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'man')
-rw-r--r-- | man/make.conf.5 | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/man/make.conf.5 b/man/make.conf.5 index 85ee88c05..dbab292fb 100644 --- a/man/make.conf.5 +++ b/man/make.conf.5 @@ -434,10 +434,6 @@ like "File not recognized: File truncated"), try recompiling the application with ccache disabled before reporting a bug. Unless you are doing development work, do not enable ccache. .TP -.B cgroup -Use Linux control group to control processes spawned by ebuilds. This allows -emerge to safely kill all subprocesses when ebuild phase exits. -.TP .B clean\-logs Enable automatic execution of the command specified by the PORTAGE_LOGDIR_CLEAN variable. The default PORTAGE_LOGDIR_CLEAN setting will |