To echo the sibling, but with some more detail: I worked on a system that (among other things) packaged up a Linux system as a network appliance. The device ra

To echo the sibling, but with some more detail: I worked on a system that (among other things) packaged up a Linux system as a network appliance. The device ran multiple daemons. I have built similar things before in a SysV world, and systemd made the following things easy: * Starting each daemon only when the system resources it needed (e.g. network up) were ready * Starting the daemons in the right order relative to each other * Putting daemon log output in syslog * Restarting when crashed (for those where it was appropriate) These all required only a few lines of systemd config, and no special coding in the application. For instance, logging was just printing to stdout/stderr and systemd took care of the rest.