site_archiver@lists.apple.com Delivered-To: Darwin-dev@lists.apple.com Lastly, StartupItems are on their way out, and unless you're seeking compatibility with pre-Tiger (10.4) systems, you'd be better off using a launchd plist. That's because the dependency mechanism is much tighter than strings. launchd allows daemons to "publish" a service via an IPC mechanism such as a socket or mach port. Clients connect to the known port, and bing! the service appears. That's all well and good if you're in control of all the variables in the equation and don't mind special-casing OS X support. That's much more efficient than starting a service and vending a name hoping someone wants to use it, or wants to wait for it. Depends. In a server environment, I'd want the service available and ready to take client connections immediately - without any startup overhead - especially if it needs to perform lengthy initialisation. -pmb _______________________________________________ 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... At 8:00 PM +0100 5/15/06, Finlay Dobbie wrote: On 15/05/06, Peter Bierman <bierman@apple.com> wrote: At 10:45 AM +0100 5/15/06, Finlay Dobbie wrote: On 15/05/06, Kevin Van Vechten <kevin@opendarwin.org> wrote: launchd doesn't have daemon dependency support, last I checked. StartupItems are already OS X only. Launchd is far more likely to become widely adopted. You can configure launchd jobs that way. Either way, the IPC channel to the service _is_ the dependency. It's less overhead and more accurate than passing around dependency "names". This email sent to site_archiver@lists.apple.com