![]() ![]() I’ve had it hang at boot, hang at shutdown, scramble error logs, prevent X from starting with no error message or log output, and a few other nasty things. And that’s been my experience systemd is occasionally buggy and does what it wants instead of what I want it to or expect it to. I’m not sure how you got “out of control monster” from my “mostly stable” description to me “mostly stable” means “occasionally unruly”, I apologize if that wasn’t clear enough. I’m curious why you picked the language “tame it” and “mostly stable” like systemd is an out of control monster. But in practice if you don’t then your software is incompatible with distros running systemd. In theory you still don’t have to use systemd or it’s tightly coupled API. If your container manager creates and manages cgroups in the system’s root cgroup you violate rule #2, as the root cgroup is managed by systemd and hence off limits to everybody else. You can still have controllers, but now they have to do through systemd’s privileged APIs and they can’t call the kernel directly. Containers can no longer directly provision their own cgroups. ![]() Like it or not though linux kernel control groups moved to version 2 and put systemd in the privileged position of managing root cgroups exclusively. There were many awesome tools including LXC employing cgroups before systemd. ![]() I’ve been burned by those things as well. Using this metric, SystemD is the worst tool for the job. The only thing I want from the init system is not to fail and be easy to fix when it does. – I tried using cgroups to set application limits only to find this mechanism is now under a sole control of SystemD, who knows what for.īooting process is trivial and in most cases unimportant – I reboot my laptop once a month, usually when I forget to plug it in. I’ve added an extra container and another unrelated and more important container stopped booting. – Only one LXC container with SystemD can run at a time. – Installed a server daemon shipped without SystemD units – half a day spent learning how to set it up just to have it running at startup. Fixed after an hour of googling on a phone. – System not booting after an upgrade due to systemd errors. I’ve been burned with SystemD several times, and it is several times too many for an init system. ![]() Since when exactly an init system needs porting? SystemD being overengineered, fragile and buggy is a fact. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |