|
|
A possible solution
Well, for all of you who tried the networking update and it didn't work (like me) try this.
I, too, have noticed a significant extension of the time it takes OSX 10.1.5 to start. It seems to pause for about 5 minutes (!) on the "Starting Directory Services" startup message. There seems to be a fair number of people experiencing startup delays. In fact I found a posting on the Apple message bards from someone who was going to replace the...
/system/library/extensions/AppleGMACEthernet.kext
...File with the one from the 10.1 update CD. I tried that with no luck. So I quickly put the newer version back.
Out of curiosity i tried starting in verbose mode (CMD-V) and got confirmation of this startup delay in glorious black and white. Note that you can see what is going on without frantically copying down what is on screen by viewing the "startup" log at:
/private/var/log/system.log
if you make a note of WHEN the pause takes place is it makes it easier to find the appropriate entries which I have listed below.
Jun 21 15:19:02 localhost lookupd: NetInfo connection timeout: RPC: Timed out on initial connection to 127.0.0.1/local
Jun 21 15:19:03 localhost lookupd: NetInfo connection timeout: RPC: Timed out on connection to 127.0.0.1/local
Jun 21 15:19:07 localhost lookupd: NetInfo connected to 127.0.0.1/local
Jun 21 15:19:23 localhost netinfod local[227]: ni_crashed's udp binder connection to ptavv[192.168.X.X]/local failed during opening (UDP) - socket_open failed
Jun 21 15:19:43 localhost netinfod local[227]: ni_crashed's tcp binder connection to ptavv[192.168.X.X]/local failed during opening (TCP) - socket_connect failed
Jun 21 15:24:17 localhost lookupd: NetInfo connection failed for server 127.0.0.1/local
Jun 21 15:24:17 localhost lookupd[234]: lookupd (version 233.2) starting - Fri Jun 21 15:24:17 2002
Jun 21 15:24:17 localhost lookupd[234]: configuration initialization failed: using defaults
Note the entries at 15:19:23 and :43. "ptavv" is an entry I made (one of many) that points to a webserver located on my local intranet (on a different Mac). Unfortunately I have NO clue as to what that error signifies. After that you can see there is a significant delay till the next message, at which point the startup proceeds at a normal pace.
I removed that particular entry in netinfo and rebooted. The Mac booted properly without the previously noted delay (as below) !
Jun 21 15:46:30 localhost lookupd: NetInfo connection timeout: RPC: Timed out on initial connection to 127.0.0.1/local
Jun 21 15:46:31 localhost lookupd: NetInfo connection timeout: RPC: Timed out on connection to 127.0.0.1/local
Jun 21 15:46:35 localhost lookupd: NetInfo connected to 127.0.0.1/local
Jun 21 15:46:35 localhost lookupd[235]: lookupd (version 233.2) starting - Fri Jun 21 15:46:35 2002
It beats the heck out of me why that one entry would cause such a delay but if you are experiencing a similar delay, check your system log for similar errors. If anyone knows exactly what happened here I would love to know.
A possible solution
It seems like NetInfo is trying to reach a parent NetInfo server, unsuccessfully.
When you created the entry for pivv (approximate spelling; your message scrolled off of my screen when I went into compose mode), did you leave a "serves" property? I've learned the hard way that the duplicate/change method of creating a new entry in NetInfo leaves the "serves" property, which is a clue to netinfo to look for another netinfo server, but is not needed for a "hosts" type entry. David |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.08 seconds |
|