site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Jun 4, 2006, at 12:22 PM, Peter Seebach wrote: -john _______________________________________________ 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... Jun 4 12:06:18 localhost launchd: localhost.script_name: getpwnam ("kodak") failed Jun 4 12:06:18 localhost launchd: localhost.script_name: exited with exit code: 1 Jun 4 12:06:18 localhost launchd: localhost.script_name: 9 more failures without living at least 60 seconds will cause job removal Does the user exist? Why, yes. This is not only a user on the system, but the user that gets automatically logged in once the system is booted. So what happens? Launchd tries to launch this before the netinfo stuff is all up, and ends up yanking it from the job list, not because the script or daemon is problematic... But because the UserName key isn't viable yet. Dependencies on directory services are problematic for all the launching methods in OSX because directory services being launched and "available" does not mean the configured data sources are available. Launchd may be failing particularly badly here, but StartupItems can too. This personally bit me with LDAP defined automounts. I eventually wrote a directory services blocker which would stall the automount daemon launch until all the sources defined in directory search were online. (Automount is *supposed* to notice when the network configuration changes, but that proved unreliable.) But is blocking until all directory service search paths are available actually the correct thing to do? Hard to say. What if one of the paths is mirror of another and it being online is purely optional and possibly not even common? What if a dependent service needs information from one path, but doesn't care about another, should it be blocked until both are available? Should the dependent dig deeper into the directory service configuration to determine which search paths have the information needed mapped? So whatever your startup method of choice is, directory services needs some finer resolution dependency targets to work well. This email sent to site_archiver@lists.apple.com