![]() ![]() System/Library/UserEventPlugins/ugin/Contents/MacOS/AirPortU serAgent System/Library/KerberosPlugins/KerberosFrameworkPlugins/SCKerberosConfig.bundle /Contents/MacOS/SCKerberosConfig System/Library/KerberosPlugins/KerberosFrameworkPlugins/Reachability.bundle/Con tents/MacOS/Reachability System/Library/KerberosPlugins/KerberosFrameworkPlugins/LKDCLocate.bundle/Conte nts/MacOS/LKDCLocate System/Library/KerberosPlugins/KerberosFrameworkPlugins/heimdalodpac.bundle/Con tents/MacOS/heimdalodpac System/Library/UserEventPlugins/ugin/Contents/MacOS/ACRRDaemon ![]() private/var/folders/td/hnt8krzc8xj63p001s61rg7r0000gn/C/mds/mdsDirectory.db System/Library/Frameworks/amework/PlugIns/csparser.bundle/Contents/M acOS/csparser In fact, looking at UserEventAgent's open files and ports in Activity Monitor, something just plain doesn't look right: This connection is immediate, and short of force-quitting UserEventAgent in Activity Monitor at the exact moment I try to eject that drive, I can't disconnect it properly without forcing it or shutting down completely. Using the "list open files" command and searching for that drive reveals that UserEvent drops an immediate hook in it for some reason. And lately, whenever I plug it in, I can't eject it without forcing it to eject. I'm running a MacBook Pro (2008-ish model) running Mountain Lion 10.8.2 with 4Gb of RAM and 750Gb of internal HD (the original 250Gb seriously cramped my style), and UserEventAgent is acting all weird.īecause of that old 250Gb HD, I was in the habit of storing files I didn't need at the time on an external hard drive, a LaCie 500Gb connected by FW800 (probably not relevant). ![]()
0 Comments
Leave a Reply. |