On Oct 19, 2004, at 11:02 AM, Michael Bartosh wrote:
I've also bumped into similar situation in the past. For the future,
would you care to share your kill-the-DS script?
Rather than killing DS, Scott Barber informed me a while back that
he'd worked around this issue by adding dependencies to the startup
items. This is on thew whole less intrusive I think. I forget exactly
which dependencies he used; iirc I made LoginWindow depend on
DirectoryServices. The latter is empty so it's a bit weird to me that
it worked.
That does seem strange that it would work. The particular issue that we
were seeing was a mis-coordination between the NFS and DS services. The
LoginWindow could auth just fine, but the mount wasn't there. So making
it wait any longer to start wouldn't do much in my mind.
But yeah, both the DS and the LoginWindow startup scripts are pretty
empty. DS just returns a clean 0 and LoginWindow just drops a marker
file for SystemStarter to see. They don't actually start anything.
FWIW this sort of fix will only work on 10.3 anyway since < 10.3 won't
do the dynamic automounting.
For all of you that want to see what I did and how I did it I should
have my article on afp today. I would just like the time to cleanup the
startupitem before the horrible, ugly version gets out there too much.
That and my article needs to be finished and go through our internal
peer-review process, but that should be quick.
