site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Our internal bug tracking the mis-feature removal is: 4458207 On Jun 4, 2006, at 12:22 PM, Peter Seebach wrote: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>localhost.script_name</string> <key>UserName</key> <string>kodak</string> <key>ProgramArguments</key> <array> <string>/path/to/program</string> </array> <key>RunAtLoad</key> <true/> </dict> </plist> This launchd item, placed in /Library/LaunchDaemons, never gets run. Why? -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/zarzycki%40apple.com _______________________________________________ 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... We're planning on (but not committing to) removing the jettison logic from launchd in the Leopard timeframe. Hmm. Well, maybe someone can tell me what I'm doing wrong with launchd. 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. It doesn't matter what's in the ProgramArguments, because the program never gets to being spawned, because the UserName doesn't work. Doesn't this mean launchd ought to, hmm. Maybe check for availability of NetInfo before trying to spawn a job, then killing it for lack of resources? If "don't just suicide when your resources aren't available" is such good advice for programs in a launchd world, why doesn't launchd follow it? This email sent to zarzycki@apple.com This email sent to site_archiver@lists.apple.com