4 ms·
> Works fine on my Gentoo (OpenRC) desktop. This meme that systemd is necessary for cgroups is simply incorrect. That's not what it's about. The point of cgrou
by vidarh 11y ago
> Works fine on my Gentoo (OpenRC) desktop. This meme that systemd is necessary for cgroups is simply incorrect.
That's not what it's about. The point of cgroups integration in systemd is that it allows systemd to precisely track the processes started under it, which means that e.g. applications where things like double-forking or similar happens can still be completely stopped by systemd even if the parent process des.
> You're trying to frame the conversation in a way that presumes features like cgroups or "socket activation" are desired features.
They are to me. They massively improves things vs. sysvinit.
> The entire point of this "debate" is that you shouldn't be tying extra features to the init process.
The entire starting point for systemd is that traditional sysvinit is woefully lacking in the functionality required to build reliable systems. And when you start trying to cobble together something on top of it, it quickly becomes clear that it is not easy.
E.g. try to build a reliable process manager outside of pid 1. You still need process restarting functionality in pid 1 for when your process manager dies. What if it fails to restart? How are you going to log those failures reliably? You end up duplicating a lot of functionality of a process manager in pid 1 if you want a reliable system even if you run a separate process manager outside of pid 1.
There are parts of the systemd design I don't agree with, and I think they'd benefit from splitting out various components from the project, not least for "political" reasons. But the design for the core parts of systemd-the-init-system largely follow on from a very limited set of core requirements of being able to reliably start, stop and keep services running and reliably log data from them.
These are requirements that sysvinit basically throws it hands up at and says "not my table", while by owning pid 1 they make it basically impossible to meet them.
- pdkl95 11y ago> The point of cgroups integration in systemd I know why systemd uses cgroups. I was addressing the myth that systemd is required to use cgroups. > They are to me. That's nice. You should use systemd if its features satisfy your requirements better than the other options. Other people have different requirements. Is this concept difficult to understand? We don't want the same features, for a variety of reasons. Disagreement is fine, but systemd advocates often seem to want a monoculture. > the functionality required to build reliable systems That's your opinion, which you're entitled to. I disagree, as I've never had problems like you're describing. I value stability a very strongly, so I consider the methods that worked fine over the past 20+ years. > requirements That's the framing I was talking about. There is more than one way to design a stable system, and your requirement list is only one of those methods. Some of those requirements I consider misfeatures that cause problems, but it's fine if you disagree. > impossible to meet them Then use systemd or some other solution that solves your needs. Is it so hard to understand that we can choose different software?
- vidarh 11y agoI'm not arguing against your ability to pick something else. What I see, however, in most of the opposition to systemd is that most who criticise it don't understand these design considerations and often aren't even aware of the problems involved. This is why they keep coming up. If most people designed systems that took care of these things in other ways, it wouldn't be so much of an issue. But most people don't. E.g. the fact that most Linux distros for the longest time kept running critical system services straight from init scripts with no process manager or other restart logic is a good example.
- digi_owl 11y agoAnd oddly enough those "services" (or daemons as they used to be called, wonder why that changed) could run for years if not decades without a hitch. But now everything seems to be a case of web monkey balls of yarn that is no better than Windows in staying upright. Its like i can reuse old UF comics, only replace Murky's love for Windows with Ubuntu or some such.