I have an app and a launchd daemon.
- The app communicates with the launchd daemon through XPC.
- The launchd daemon is triggered by the XPC "message" and exits after having completed its task.
Problem:
When I repeatedly launch the app, launchd is not happy with the fact that the daemon only runs for around a second and starts complaining in system.log with:
Service only ran for 5 seconds. Pushing respawn out by 5 seconds.
Service only ran for 7 seconds. Pushing respawn out by 3 seconds.
And sure enough launching and getting an answer from the launchd daemon is delayed at some point.
Question:
Is there a key to put in the launcdh plist file or a function to call from the launchd daemon to explain to launchd that this is the expected behavior for the daemon and that it should not delayed its next launch?
I've checked the launchd.plist man page but have not found anything enlightening so far.