On Jun 8, 2006, at 10:56 PM, Ryan McGann wrote:
Now that the launchd discussion has died down, I guess it's time
to kick up the ashes with an honest question. We are using launchd
in Tiger to startup our daemon. It is currently not load-on-
demand, so it gets launched very early. It's usually process ID
18-25.
We seem to be experiencing some problems in Tiger related to how
early we get started. In particular, the following APIs seem to
rely on daemons to perform their dirty work, but those daemons
are not ready when we use them:
- The Carbon Alias Manager which is used to determine the
location of some files saved in the preferences accessed by our
daemon. Sometimes the Alias Manager fails to resolve the aliases,
even though they point to files that have not changed. We are
using FSResolveAliasNoUI to resolve the alias in our daemon.
Carbon is not daemon-safe, so you're SOL there. Tech Note 2083:
<http://developer.apple.com/technotes/tn2005/tn2083.html>
