180
SystemD
(lemmy.ml)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
My problem with systemd is that since I'm practically forced to use it that it's flakey in starting services after boot (independent of service and distro). Since systemd I had to install monit to check if all services came up. Didn't had that problem before. Or I forgot, it's been a while....
Don't worry about the downvotes, Lemmy is a systemd sausage fest. If you want negative "karma", just write "systemd bad" or even "pulseausio bad" anywhere, and wait...
Well yes, if you don't provide intelligible arguments it doesn't deserve better. And a lot of the arguments really are like that: "systemd bad" or "is monolithic blob" (which it isn't).
Lol. Thanks. I really don't care. I'm running linux servers professionally since the late 90s, which means I have seen one or the other WTF. And systemd had quit some of them, especially flooding log files and race conditions. For example see https://github.com/systemd/systemd/issues/7293. That took more than 2 years to fix. And if people like to downvote my personal experience with it they are welcome to do so. I mean all I did was answering a question why one might use a systemd free distribution. Oh and for the downvoters: SYSTEMD IS MICROSOFTS ATTEMPT TO KILL LINUX! Poettering always was their agent. https://en.m.wikipedia.org/wiki/Lennart_Poettering 😉
systemd does have one problem that also existed before: sometimes services come with buggy unit files (or copy/pasted from something else and modified), similar to how there were all kinds of buggy scripts before. Unit files are much simpler than scripts and it should be easier to get right but when the author sometimes doesn't consider dependencies or test fail scenarios...
Use
systemctl --failed
to see which services didn't come up,systemctl status SERVICENAMEHERE
to see some status info about a service, andjournalctl -b -u SERVICENAMEHERE
to see all log messages generated by a service since last reboot.