3 ms·
systemd has its place, and that is "Linux on the desktop." Say what you will about it being a pain in the ass to debug or maintain or how it eats every Unix ser
by striking 12y ago
systemd has its place, and that is "Linux on the desktop." Say what you will about it being a pain in the ass to debug or maintain or how it eats every Unix service in order to grow like a Katamari, it works beautifully for package maintainers to keep everything in order. If you like `apt-get install`s or `pacman -S`es, this really helps those who need to keep that in order.
However, I would never, ever, recommend it on a server. Unless you've got some sort of really complex deployment, get a barebones kernel and SysVinit and put it on a read-only FS. Do you need any more than that?
- XorNot 12y agoDeploying custom services on systemd requires a 5-line service file, only 1 of which is not boilerplate. If it works as a foreground service, then it'll work as a start-up service and your logging will go into syslog correctly. The "it's too heavy" argument doesn't hold much water either. I've not yet heard a realistic description of a lightweight server which can actually be a practical server.