site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Jun 3, 2006, at 12:25 PM, Jordan K. Hubbard wrote: On Jun 2, 2006, at 10:17 PM, Peter Seebach wrote: __ Michael Bartosh http://www.4am-media.com London through 6/7 Tokyo 6/8-14 _______________________________________________ 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... And since 10.4, getting even fairly trivial daemons started at a time when the system provides the services they need is annoying, and following the instructions given in the man page can wedge a system permanently at a blue screen. I didn't say it was impossible; I said I didn't think it's a "good tool". It's obviously possible to do the bootstrapping that way; I just don't think it's a very good tool for the job. Maybe this whole conversation would be easier if you (and some of the others in this conversation) could more precisely describe just what it is you want launchd to do, rather than making this an ongoing retro argument where we stick on our grey beards and debate the usefulness of StartupItems, /etc/rc.d, SYSV runlevels and so on. a) allow launchd.plist items to key off of configd events, like configd's kicker (a facility I use frequently) can. This would permit developers to use this relatively innovative facility without having to write any Mac OS X specific code. b) have a 'requires' item in launchd.plist, ie 'requires org.mysql.mysqld' Provides could implicit with the job's label. Yes, you can write wrappers, but why? That makes things harder to deploy in Tiger. Feel free to remove b) in 5 years. But tell us now. We need a road map in enterprise deployments. WRT a) I've heard that Apple doesn't want to link launchd against higher level frameworks. But that goal seems contrary to launchd's kitchen sink model (and I don't say that disparagingly). AND it (a) would be super cool, and useful. This email sent to site_archiver@lists.apple.com
participants (1)
-
Michael Bartosh