Memory caps, run time limits, sleep inhibitors, better cron and path units - systemd features that turn out to be handy for running throwaway agent-written code.
I mean, the only thing i needed cgroups for was running rootless containers on Alpine (Openrc). This was something like cgroups = true in their main config. Can it be easier?
Ok and now tell me how to use cgroups for a random binary, anything that has not buildin cgroups support.
That’s were it gets complicated and where systemd can help a lot
You are using a tool where someone else has solved the hard part to show that no hard part exists in the first place.
Yes, that is one of the tools needed.
But it is not helping with doing anything meaningful with cgroups.
A cgroup without any kind of specific configuration is almost as good as no cgroup at all.
That’s what I meant with the hard part.
And I did say that systemd makes it stupidly easy, in contrast to the normal easy that cgroups often are.
I mean, the only thing i needed cgroups for was running rootless containers on Alpine (Openrc). This was something like
cgroups = truein their main config. Can it be easier?Ok and now tell me how to use cgroups for a random binary, anything that has not buildin cgroups support. That’s were it gets complicated and where systemd can help a lot
You are using a tool where someone else has solved the hard part to show that no hard part exists in the first place.
I mean, what use is cgroups if you don’t need it? And what needs it is usually a tool. Tool has it preconfigured for it’s needs, so, easy.
So you think that every Linux application comes with it’s preconfigured cgroup configuration?
Well then, ok
Yes, that is one of the tools needed. But it is not helping with doing anything meaningful with cgroups. A cgroup without any kind of specific configuration is almost as good as no cgroup at all. That’s what I meant with the hard part.
And I did say that systemd makes it stupidly easy, in contrast to the normal easy that cgroups often are.