On Tue, 25 Nov 2014, Louis Kowolowski wrote:
After reading http://boycottsystemd.org, I’m curious who thinks that systemd is an improvement for servers, and if so why/how. Are people running CentOS 7 on servers yet?
I've got CentOS 7 and Fedora 19 on servers, so I've been working with systemd for a while.
It didn't take me all that long to revamp my cfengine rules to deal with systemd; the rulesets are similar:
"/sbin/service" args => "sendmail condrestart"; becomes "/bin/systemctl" args => "restart sendmail.service";I don't yet understand all the ins and outs of systemd. I have a good handle on the .service units, but the others (.mount, .path, .scope, .socket, .device, and even .target) are still works in progress.
The systemctl binary, while not intuitive at all, is easy to learn and provides a consistent interface to things. I do not miss init scripts at all. The boycott page conveniently overlooks all the init scripts that broke, badly, when Ubuntu decided to make /bin/sh a version of dash rather than bash. System V on modern Linux systems is very tool-dependent as well.
I'm not a fan of journald and I always setup rsyslog to ensure I have text log files, but that's the only long-term downside I've encountered so far.
One of my holiday projects is doing the systemd version of Linux From Scratch, just so I have a better basic understanding of its capabilities and competencies.
I like the possibilities of systemd, but I can see the downsides as well. At this point, I don't see any reason whatsoever to get all worked up about the change. It seems to work, which is all that I ask of it.
-- Paul Heinlein [email protected] 45°38' N, 122°6' W
_______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
