systemd units allow to run processes in foreground while daemonization is done on systemd service level when using Type=simple (default). This allows systemd to reliably track the service state, signals and could catch outputs, i.e. it is possible to remove "--quiet" to have Tautulli logging to systemd journal (journalctl) additionally or alternatively to log files.
In case of Type=forking, a PID file is required to allow system reliably determine the service state, which would be an alternative, but has no real advantage. The solution with "GuessMainPID=no" allows systemd to correctly determine the service active state, but e.g. when it is killed, it is seen as "Succeeded." since systemd cannot track the exit code or signal.
Skip the extra process calls trying to figure out what to run Tautulli
with, as well as give an example on how to change the executable in the
init script.
Edited user creation and directory ownership instructions in the configuration notes for clarity. Current version may give novice users the impression that the ownership command is only executed on CentOS/Fedora.
If the process fails 3 times within 90 seconds of a start attempt
consider it permanently failed and stop all further attempts to restart
it automatically.
If Tautulli ever crashes due to a failure of some sort the policies
mentioned here will automatically restart it, with the caveat that they
will _always_ restart it, even if it is going to crash right away again!
