Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I suppose that because because of the updated way that the Calendar application is integrated into the OS X system and the notification area the "calendar agent" needs to constantly run in the background on OS X ML.

I see it making a lot of requests when I debug the HTTP(s) requests on the system:

screenshot-with-shadow.png

The requests stop if I do killall CalendarAgent:

Picture 2.png

How can I keep the calendar agent from running in the background?

ps: I also tried removing the calendar from the notification area without luck:

screenshot-with-shadow.png

share|improve this question
add comment

3 Answers

up vote 7 down vote accepted

You can try like this:

launchctl unload /System/Library/LaunchAgents/com.apple.CalendarAgent.plist

If you want to make this permanent:

launchctl unload -w /System/Library/LaunchAgents/com.apple.CalendarAgent.plist

Hope it helps!

share|improve this answer
    
It doesn't work (with nor without sudo) launchctl unload -w /System/Library/LaunchAgents/com.apple.CalendarAgent.plist produces launchctl: Error unloading: com.apple.CalendarAgent because that's apparently not the agent that's running: launchctl list|grep -i cal and i get 76977 - 0x7fbf59e07fa0.anonymous.CalendarAgent. I've force quit the agent, manually disabled it in the plist, remove all notifications, and calendar system preferences settings yet it still returns. –  nix Jul 12 '13 at 3:07
    
I also disable Calendar in the Spotlight Preferences yet still the CalendarAgent is magically starting. –  nix Jul 12 '13 at 16:13
add comment

Within 10.8.4 (12D78) doing: launchctl unload /System/Library/LaunchAgents/com.apple.CalendarAgent.plist without sudo works fine.

I only get: launchctl: Error unloading: com.apple.CalendarAgent with attempting sudo....

share|improve this answer
1  
I can't tell if this is an answer or a comment... –  Taegost Jul 31 '13 at 12:47
add comment

There may be a previously entered password for the process in your login Keychain. You may have to remove a key or certificate using the Keychain Access utility.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.