site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On May 23, 2006, at 2:23 AM, Peter Seebach wrote: So, say, you add a tag like <key>StartupDone</key> <string>Gzornenplatzen</string> in some plists, and in others, you have <key>StartupAfter</key> <string>Gzornenplatzen</string> - Kevin _______________________________________________ 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... Well, that suggests a way to resolve this fairly elegantly; just provide a hook in plists for having services Do Something which causes other services to run. Bam. Nice generic way to put the "something happened and I want to be run" *IN LAUNCHD WHERE IT BELONGS* rather than having all the applications sit around inventing new notification methods and writing their own code. Sure, but the issue you're overlooking is that there's no universal definition for when startup is done. Disk and network availability are events, like keystrokes. When do you know that keyboard input is done? You could possibly wait for the keyboard to be quiescent. You could alternatively look for a marker like newline. But you'll never get an EOF. While I agree with you that sample code / libraries would be help applications approximate when startup is done (just like Libc provides line-buffered stdin), I disagree that this belongs in launchd itself (or keyboard device drivers). Launchd triggers are unambiguous and discrete, there isn't really room for interpretation. Adding in keys like "StartupDone" changes that. This email sent to site_archiver@lists.apple.com