3 ms·
You can also just freeze the whole cgroup, and then the kernel will cascade it to all tasks within said cgroup, and then you can do process management. Most of
by TheDong 10y ago
You can also just freeze the whole cgroup, and then the kernel will cascade it to all tasks within said cgroup, and then you can do process management.
Most of what you complain about though is solved by duplicate pids not being assigned in short succession (which is generally true, though in reality is an implementation detail of linux which is not promised).
- JdeBP 10y agoI was expecting someone to mention the freezer. Not only does systemd not use the freezer, but the systemd people explicitly describe it as having "broken inheritance semantics of the kernel logic". You'll have to ask them what they mean by that, but the freezer does not, for them, magically turn cgroups into a job mechanism either. Which leads to another point. If you think that this is my complaint, you should read the systemd people on the subject over the years. They were rather expecting (version 2) cgroups to be a true job mechanism, and they've complained every time that it has once again turned out not to be. Moreover: this is not to mention that Docker and others will manipulate the freeze status of control groups for their own purposes, and there is no real race-free mechanism for sharing this setting amongst multiple owners, such as an atomic read-and-update for it.