site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com In message <515DFA89-A274-41AD-AFC1-A25B82EF735E@apple.com>, "Jordan K. Hubbard " writes:
I think I got that part already, but we need to get more specific. HOW should it handle the dependencies (in ways not already provided for)? What ARE those dependencies? That's the kind of detail I'm asking for. The above sentence qualifies more as a mission statement than a specific set of goals, and we've already been all over the mission statement side of things in this thread.
Okay. I think the obvious ones are "network started" and "device drivers loaded". Yes, it's always possible there are later changes; however, for a huge variety of real-world apps, "at least one network interface up and at least one host name assigned" is good enough.
So, it'd be REALLY NICE if launchd provided at least a few basic hooks so that the easy cases would Just Work.
If you'd enumerate some of these hooks and "easy cases", that would be helpful.
The most obvious dependencies are specific services (we can sort of do this already), network, and host name.
Cool. Clean it up, give it a man page, and include it in the system, and we should be all done.
You're certainly jumping rather eagerly on my solution without knowing what it actually does. That's either a testament to your enthusiasm or a worrying sign that you don't know what you actually want. :-)
Well, a wrapper that lets people express dependency relations even among their own programs would be a good start.
Apple HAS provided this already. That's what IPC-based launching is all about - when something is actually needed, use the interlock that IPC gives you to launch it and allow it to satisfy the request. You're saying that's not enough, so please provide details as to what you'd like to see (and when I say "details" I mean "something that someone could actually start implementing", not "I want a system that Does The Right Thing, dammit!").
What I want is exactly what launchd is trying to foist off on me; the ability to put requirements OUTSIDE THE CODE so I don't have to maintain dozens of copies of the code. -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/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com
participants (1)
-
seebs@plethora.net