Introducing /run

Most init.d scripts were buggy as hell. When I write my daemon code I always include command line arguments to specify PID, config, chroot, and log paths and all the other options that cannot be done easily or safely outside of the actual daemon itself. Inevitably someone would come along and rewrite my very simple init.d script (which simply forwarded options to the actual daemon to be done *properly*) to use the inherently broken init.d shell function libraries of various distributions.

I'm not the biggest fan of systemd because it's yet another incompatible daemon manager (compare OS X launchd, Solaris SMF, daemontools... and OpenBSD is just *now* moving to rc.d scripts for ports!) But in most ways it's an improvement over the _existing_ init.d systems. init.d itself isn't broken, IMO, but Redhat especially--other distros, too--made it broken by trying to use it to paper over all the deficiencies in other people's broken code, rather than *fixing* the broken code.