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.
You may have experienced this before. You have an agent write a script, perhaps to do some data analysis. It has a terrible memory leak, and suddenly your machine freezes and (hopefully) the kernel resumes after a bit with an OOM error I’ve had this a few times, and it’s very annoying…
Holy fuck I can’t stop laughing at their reason for systemd for some reason, probably need an agent summarising their article for me
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 remember way back when I was doing Ruby on Rails, we would always wrap the server processes in a manager (I forgot what it’s called) that watches the memory and restarts them when the leaks get too bad. What a ridiculous solution that was.
This has been happening forever. This old post always pops up in my mind for some reason as a historic example from an earlier linux boom.
Unfortunately, people have been pushed to not call out such things, because it’s “not nice”, when as the blog above shows, not calling it out is what’s not nice, and potentially dangerous.
Yeah. I called out someone here on Lemmy for just completely making shit up about some kernel feature, linked the documentation showing the actual meaning, and got downvoted for it.
Which cron?
Oh wait. Why did I assume OP would know there are multiple implementations? 😄
Holy fuck I can’t stop laughing at their reason for systemd for some reason, probably need an agent summarising their article for me
He also implies that cgroups are a systemd-only feature.
But to be fair, systemd makes using cgroups stupidly easy
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.
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 remember way back when I was doing Ruby on Rails, we would always wrap the server processes in a manager (I forgot what it’s called) that watches the memory and restarts them when the leaks get too bad. What a ridiculous solution that was.
This has been happening forever. This old post always pops up in my mind for some reason as a historic example from an earlier linux boom.
Unfortunately, people have been pushed to not call out such things, because it’s “not nice”, when as the blog above shows, not calling it out is what’s not nice, and potentially dangerous.
Yeah. I called out someone here on Lemmy for just completely making shit up about some kernel feature, linked the documentation showing the actual meaning, and got downvoted for it.