Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Beware 10.7.4 update on case-sensitive systems

The new /System/Library/LaunchDaemons/com.apple.flashupdater.plist wants to run /usr/libexec/flashupdater, but there is no such file. There *is* a /usr/libexec/FlashUpdater but that's not the same name.


I only found that after the update went broadly bad on a machine running Server and sent me diving into logs, but after looking I also see it on my laptop (a pretty simple machine NOT running Server) This seems like a sign that someone was asleep at the switch in Apple QC for this update. I have not yet figured out the Server problems, which are baroquely wierd.

iMac (27-inch Late 2009), Mac OS X (10.7.3)

Posted on May 14, 2012 7:26 PM

Reply
7 replies

May 15, 2012 9:11 PM in response to billcole

As a quick fix until the next update, I modified the plist file to change the path of the executable to match that found in tthe filesystem. I suppose you could also create a softlink in the file system from the misnamed file to the real file, but that would break any backup of the files to a non-case-sensitive filesystem.


After the change, the module should be re-loaded. I just rebooted.

Jun 14, 2012 12:48 AM in response to billcole

To help someone searching to fix log entries, my console log was filled with these messages every 10 seconds:


com.apple.launchd[1](com.apple.flashupdater[19032]) posix_spawn("/usr/libexec/Flashupdater", ...): No such file or directory
com.apple.launchd[1](com.apple.flashupdater[19032]) Exited with exit code: 1
com.apple.launchd[1](com.apple.flashupdater) Throttling respawn: Will start in 10 seconds



This isn't just a 10.7.4 issue. I had exactly the same problem on my Snow Leopard 10.6.8 system. I did as George suggested - edit the .plist file ( I used TextWranger which used dialog boxes to change the permissions rather than having to remember and run Unix commands).


Only gotch was I forgot about CamelCase and didn't remember to Upcase the "U"pdater - silly me.


After reboot, ofending files were gone and no more annoying messages in my console log.


Thanks George.

Beware 10.7.4 update on case-sensitive systems

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.