On Fri, May 3, 2013 at 8:06 PM, Andy Bradford
> You can also choose to ignore ``best practice'' and install something
> sensible like daemontools/runit to supervise your daemon.
>
> daemontools is infinitely superior to ``init scripts'' and not nearly as
> complex as the new ``best practice.''
I'm not sure what you're referring to as the new "best practice", but
if you mean systemd, it's really not all that complex. The only
complexity it's got is that which is inherent in the problem of
starting up and shutting down a bunch of interdependent services as
quickly and cleanly as possible. It's managed by a bunch of symlinked
text files, not too differently than other init systems are. The
organization is a bit different, but it's not all that hard to pick
up.
I really like systemd for the fact that it eliminates shell scripts
from the bootup process, which makes for a huge reduction in overhead
on low-resource systems. I also like the way that you can put
resources like disks, network links, sockets etc. into the system so
that units can automatically launch or shut down based on their
availability.
I'm sure daemontools is just as wonderful as all the other DBJ tools,
and with a glance at the advocacy link it doesn't seem too far off in
general concept from systemd (although it is smaller in scope and thus
simpler). But unless you're building your own distro, it is probably a
better use of your time to learn to work with the init system your
distro provides, even if it is a conglomeration of shell scripts.
--Levi
/*
PLUG: http://plug.org, #utah on irc.freenode.net
Unsubscribe: http://plug.org/mailman/options/plug
Don't fear the penguin.
*/
