site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com 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? Always, JP _______________________________________________ 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... On Jun 4, 2006, at 7:48 PM, Peter Seebach wrote: In message <55267361-1F7D-437E-82C3-BE7141769224@mac.com>, johnsmailinglists@ma c.com writes: 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." -- 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 This email sent to site_archiver@lists.apple.com