Re: launchd APIs
Re: launchd APIs
- Subject: Re: launchd APIs
- From: Dave Zarzycki <email@hidden>
- Date: Tue, 25 Apr 2006 08:10:28 -0700
On Apr 21, 2006, at 2:15 PM, Kevin Brock wrote:
The only specific questions I have now involve load order.
I'm writing a daemon which needs to load automatically at boot time. It's not required (so far) by anything else that loads automatically.
It communicates with a kernel extension which loads at boot time, and ideally the daemon would load as early as possible. Is there a way to tell when launchd will try to load a daemon in the absence of others which depend on it?
No, and that is a feature in fact. :-)
launchd is a completely different bootstrapping philosophy.
Under launchd, dependancies are expected to be expressed via APIs, and those APIs may (or most likely) will use IPC to determine when goals have been satisfied.
The nice thing about APIs is that it encourages daemon writers to register callbacks for when their requirements are satisfied, which could be 30 seconds from now, or 30 days from now, it doesn't matter. But at least the daemon can make forward progress with other goals in the interim.
In your case, it sounds like you need to use the available kext management APIs to determine when your driver has been loaded.
I hope all this makes sense.
davez |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden