Most init systems are like a 21st century car, so crammed full of smog equipment, computers, and other geegaws, that you need to have specialized tools and training to do the most mundane maintenance on them.

Except for starting daemontools itself, daemontools works the same in any Unix like environment.Īs a matter of fact, even though the first sentence of this chapter mentioned systemd as a motive, it's also true for all the init systems.

Every daemon you run out of daemontools is a daemon you can control with the svc command and examine with the svstat and svok commands, whether on systemd-mandatory Red Hat, systemd-verboten Funtoo, or any BSD. Every daemon you move out of systemd and into daemontools is another daemon whose log files you can read in text mode, natively. However, if you're anything like me, many of your daemons are rather independent.Įvery daemon you move out of systemd and into daemontools makes systemd a little less complex. At least you can't do it without some serious kludging. daemontools will never replace systemd, or any other init software, because it doesn't natively handle dependencies like 'don't start Apache until the DNS server is started'. Daemontools can do a lot of what systemd can do, in one tightly encapsulated, easy to understand, ingeniously simple package. With the impending Linux switch to systemd, daemontools by djb ( Daniel J.

Transitioning a Daemon From Your Current Init.

Pro Troubleshooting Move: The xtermd Service.

Daemon tools linux