Comment 8 for bug 999698

When running in a loop like that, systemd does not guarantee that the process has actually finished starting up. systemd checks for the pidfile to make a determination when to start dependent processes. The proper solution would be for the systemd devs to fix the problem, but it is unclear if they intend to, as they think the pid lockfile is consistent with the daemon being in a runnable state. The proper semantics of the lock file should be "the daemon has started, no new ones can start now". This problem pervades all of Fedora init scripts now for dependent services.