Hello, This is a follow-up to the bug report at https://github.com/systemd/systemd/issues/39818, which is currently marked as “not a bug.” We now understand the default behavior and can adjust our slice parameters as needed, but I would like to start a discussion about the implications of this default.
Specifically: doesn’t the default behavior pose a risk to the parent hierarchy? Since the CPU controller is disabled at the slice level, a malicious or misbehaving service that becomes aware of this could fork large numbers of CPU-intensive processes. Because the parent slice does not enforce CPU limits, this could cause other services within the same slice to starve. Shouldn't the CPU controller be "turned on by default" like the PID controller? Appreciate any clarification you can provide. Thanks, Umut
