site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com In message <r02010500-1046-7F8F2912F4CD11DA99380016CB8A5B30@[192.168.1.6]>, fle tcher sandbeck writes:
For example, if the service can only be used when a user is logged in then there's no point in it launching until a user actually tries to use it. At that point they are guaranteed to be logged in. The dependency is built into the fact that the service doesn't launch until actually needed. Launchd may be having a problem launching the service at startup, but a better question may be why is the service configured to launch at startup at all?
Sorry, my description was unclear. Conceptually, there is do dependency on a user being logged in. In fact, on a slower machine, the job runs fine either way. On THIS machine, a race condition causes the job to be launched before NetInfo is available, so the UserName key can't be processed, because there's no such user -- indeed, there's no users at all. The effect of automatic login is to change the speed at which various other events happen such that the race condition isn't hit. -s _______________________________________________ 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... This email sent to site_archiver@lists.apple.com