Q: launchd, UserEventAgent sucking my CPU dry after Yosemite upgrade
I've seen a couple other posts about this, but they haven't fixed the problem for me.
Background:
I have a 2012 rMBP, fully loaded.
Two user accounts, one for work, one for home.
After install of Yosemite (from work account), everything seemed fine. This issue only occurs in my personal account.
I narrowed the issue down to a plist file from my company's MDM software (AirWatch) that is failing to launch. The system log says this (x'd out my company user ID for obvious reasons):
"10/20/14 8:36:17.961 PM com.apple.xpc.launchd[1]: (com.airwatch.mac.agent[66517]) Could not find and/or execute program specified by service: 2: No such file or directory: /Users/xxxxxx/Applications/AirWatch Agent.app/Contents/MacOS/AirWatch Agent"
There are HUNDREDS of these messages and it seems to continually try to launch the stupid thing. I think the problem is that it's trying to launch an application from another user account that it does not have access to (since the MDM software is only installed in my work account, as you can see above). The thing that confuses me is that the plist file did not change between Mavericks and Yosemite, so why does it do this now? Is there something in the plist that could impact how the Yosemite launchd tries to execute application-specific launch services? I guess I'm asking if the issues lies in the AirWatch plist file or the Yosemite launch daemo
Any ideas on how to fix this??
MacBook Pro (Retina, Mid 2012), OS X Yosemite (10.10)
Posted on Oct 20, 2014 6:45 PM