4 ms·
I used to hate systemd until we adopted CoreOS at our last job, which forced me to learn it. I have evolved and now love it. Once you learn the basics, gettin
by chrissnell 9y ago
I used to hate systemd until we adopted CoreOS at our last job, which forced me to learn it. I have evolved and now love it. Once you learn the basics, getting new services up and running with it is easy.
I really like the other parts of the systemd ecosystem, too. journald makes it easy to view the logs of any given app/service without having to hunt through directories.
I also love systemd-networkd--it's a HUGE improvement over older attempts at managing network connections. I got my start on Linux in the < 1.0 kernel days and distros back then forced you to manually configure your interfaces. This was actually really nice because it was simple and reliable. When more modern distros came along, they introduced "fancy" network management which was complicated, inflexible, and often flaky. systemd-networkd restores sanity to network interface management.
Finally, there's a great message bus that allows for API-driven interaction with various systemd components. With a good language binding, it's now pretty straightforward to tie your custom code into some of the systemd components.
- Frondo 9y agoOh, yes. I never really wrote a ton of systemv init scripts, but I wrote enough to always find it kind of a pain. Writing systemd units by comparison? Heavenly. What really sealed the deal for me was when I needed a service to automatically restart itself if it died. Restart=always, RestartSec=10, done. If it dies, it's back up in 10 seconds. I wouldn't even know how to do that with an init script, and though of course I could write something out with enough time and patience, how could that be an improvement over two easily-understood lines?
- kpcyrd 9y agoI don't know why this is getting downvoted. I used to install systemd from backports on wheezy only because I don't have to write sysv-init scripts that way.