• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: StartupItems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: StartupItems


  • Subject: Re: StartupItems
  • From: email@hidden (Peter Seebach)
  • Date: Sat, 03 Jun 2006 15:15:57 -0500

In message <email@hidden>, "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      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: StartupItems (From: "Jordan K. Hubbard" <email@hidden>)

  • Prev by Date: Re: StartupItems
  • Next by Date: Re: StartupItems
  • Previous by thread: Re: StartupItems
  • Next by thread: Re: StartupItems
  • Index(es):
    • Date
    • Thread