Thus said Levi Pearson on Fri, 03 May 2013 20:49:23 -0600: > 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.
I'm not sure what S. Dale Morrey meant by new ``best practice'' but I suppose to me it means whatever init du jour is on the menu. By comparision, I have always been able to have a consistent interface to starting/stopping daemons. I have used daemontools on Solaris, HP-UX, UnixWare, (maybe AIX, don't remember), Linux, and BSD. Doesn't matter what OS I'm on, it just works the same. I use it to supervise Apache, PostgreSQL, MySQL, djbdns, and various other daemons that I use. > 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. Usually I spend enough time with it to figure out how to integrate daemontools. Then everything works. :-) But, the nice thing about the Unix way is that there are dozens of options. I merely wanted to share some a somewhat different---but potentially useful---method for handling daemons. Doesn't mean anyone else has to use them. Andy -- TAI64 timestamp: 400000005184847b /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
