Re: StartupItems
Re: StartupItems
- Subject: Re: StartupItems
- From: email@hidden
- Date: Mon, 5 Jun 2006 11:47:18 -0700
On Jun 4, 2006, at 7:48 PM, Peter Seebach wrote:
In message <email@hidden>,
johnsmailinglists@ma
c.com writes:
Well, if the service that listens on 1234 wasn't ready... then your
service would block. How does this result in your service seeing
"sorry, no such service?
Except that sometimes, instead of blocking, you get a connection
refused.
For instance, as a concrete example, a friend's mini will fail to
start
a certain job unless you have autologin on. If autologin is off,
launchd
tries to launch the job, which has a UserName key, before NetInfo
is properly
up, and FAILS. The job gets cancelled because it can't be started,
because
the user doesn't exist yet.
This is launchd failing to ask for a service that its using: netinfo
is up and running. This is a bug, not a design flaw. File a bug
report. See Dave Zarzycki's recent post about the jettison logic.
(I assume it's a race condition.)
It seems that this is where your desire comes from for sequenced
execution during startup. Don't assume. Ask. You would have avoided
this whole thread, might have received a more constructive answer,
and would have gotten the simplest one: "this is a bug, we're working
on it, sorry."
Always,
JP
--
A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools. - Douglas Adams, Mostly Harmless
_______________________________________________
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