Why would you do that? If you're designing for systemd, go for "simple" (that is, don't fork), or if you need to signal when your service is truly ready rather

Why would you do that? If you're designing for systemd, go for "simple" (that is, don't fork), or if you need to signal when your service is truly ready rather than just monitor its lifetime, go for "notify" (or "dbus" if you're into that sort of thing). Using "forking" as readiness protocol doesn't make sense. Unlike "notify", it doesn't signal readiness. It's only there to try to understand old services that always daemonize, which was only done because the old init systems required it. Daemonizing is pointless under systemd or other init systems that handle this themselves.