site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Jun 9, 2006, at 5:02 AM, Shaun Wexler wrote: On Jun 8, 2006, at 10:56 PM, Ryan McGann wrote: Carbon is not daemon-safe, so you're SOL there. Tech Note 2083: <http://developer.apple.com/technotes/tn2005/tn2083.html> -Eric _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... 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. The Alias Manager is part of Core Services, so it should be OK. But it does require that coreservicesd be up and running.... This email sent to site_archiver@lists.apple.com