Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Panther change in StartupItems' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Panther change in StartupItems
Authored by: pjw on Nov 06, '03 03:01:00PM

So I was curious about what Resolver actually is, so I looked through /System/Library/StartupItems for the item that provides it. The item DirectoryServices is the culprit, but if you look closely, this startup item doesn't do anything. The entire script for starting up Directory Services is this:

#!/bin/sh
exit 0

That's it. I didn't find lookupd or netinfod.

Now is a good time to mention that I'm running Panther. So out of curiosity I took a look in my archived system files to see what DirectoryServices did under Jaguar. Bingo! It loaded lookupd.

So I keep investigating and I discover two directories that are new to Panther: /etc/mach_init.d/ and /etc/mach_init_per_user.d/. Apparently the startup process in Panther has changed to include loading all of the commands mentioned in the .plist files in these directories. There is a DirectoryServices command and a lookupd command -- note that they refer to two different daemons.

I'm still investigating, but I thought the power users out there might be interested to see these changes. Plus, if anyone has any information that discusses this change -- like why it was done and what the difference is between loading things from StartupItems versus the mach_init.d directory (which, by the way, doesn't seem to have any kind of ordering information), then I'd love to read more about it.



[ Reply to This | # ]
Panther change in StartupItems
Authored by: pjw on Nov 06, '03 03:31:29PM

I found confirmation of this change. Perhaps this should be listed in a different hint. Apple is phasing out the StartupItems mechanism for loading daemons and services and moving to a "load-on-demand" approach that uses a tool called register_mach_bootstrap_servers. Here's the document that gives the details:

System startup: The Boot Process (Bootstrap Daemons section)

I have no idea how this impacts where the Firewall startup should go.



[ Reply to This | # ]