Take a look at your Console log

SilentCrs

macrumors regular
Original poster
Nov 2, 2006
215
0
Do you see the following:

10/28/07 1:06:33 AM com.apple.launchd[1] (com.apple.dyld) Throttling respawn: Will start in 59 seconds
10/28/07 1:07:33 AM com.apple.launchd[1] (com.apple.dyld) Throttling respawn: Will start in 59 seconds
10/28/07 1:08:34 AM com.apple.launchd[1] (com.apple.dyld) Throttling respawn: Will start in 59 seconds
10/28/07 1:09:35 AM com.apple.launchd[1] (com.apple.dyld) Throttling respawn: Will start in 59 seconds
10/28/07 1:10:39 AM com.apple.launchd[1] (com.apple.dyld) Throttling respawn: Will start in 56 seconds

I've seen this on every machine I've installed Leopard to (all Erase and Installs).

What's going on here?
 

stannenb

macrumors newbie
Oct 28, 2007
4
0
I'm seeing it, too

What's happening is that the dynamic linker is trying to start up,
it fails, launchd does its job and tries launching it again, it fails...

Then launchd notices that it's trying to launch it a lot, and slow
things down.

The question is why is the dynamic launcher failing.
 

stannenb

macrumors newbie
Oct 28, 2007
4
0
The fix

Run:

update_prebinding -force -root /

FWIW, the problem seems to be triggered by the first sotware update,
not the initial Leopard install.
 

stannenb

macrumors newbie
Oct 28, 2007
4
0
Can you explain...what exactly is this command doing?

-Kevin
It's a forced update of dyld's cache. It actually runs
update_dyld_shared_cache.

Type "man update_prebinding" from Terminal for all
the gory details.

Presumably, something is corrupting the cache, and a forced
rebuild deletes and rebuilds it, eliminating the corruption.
 

netnothing

macrumors 68040
Mar 13, 2007
3,674
304
NH
Ran that command, but still got the errors.

A reboot seems to have fixed it (for now).

-Kevin
 

netnothing

macrumors 68040
Mar 13, 2007
3,674
304
NH
Anyone know why after updates in Leopard that require a reboot (like the QT update or tonights security update)....I still get this error in the Console logs?

All I have to do is reboot a second time and the message doesn't seem to come back.

It looks as if it just happens after the first reboot.

-Kevin
 

netnothing

macrumors 68040
Mar 13, 2007
3,674
304
NH
Just thought I would update this thread. It does look like this is an issue AFTER a software update....as it is still happening for me. I did run into this tech note from Apple:

http://developer.apple.com/releasenotes/DeveloperTools/RN-dyld/index.html

The interesting part is this:

#dyld shared cache
Mac OS X 10.5 no longer uses prebinding for the OS itself. Instead a “cache” file is built from commonly used dylibs. The cache is automatically rebuilt whenever one of the dylibs in the cache is updated (usually just during a Software Update). When the cache is built, the addresses of the dylibs are intentionally randomized, thus when debugging you may notice that the address of OS routines like malloc is different on every machine.
So I am thinking that this is just an issue within Leopard on the first reboot after installing a SU. And it seems to go away after another reboot.

-Kevin
 

Similar threads

  • VictorTango777
0
Replies
0
Views
337
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.