I am thinking of deleting some contents from /usr/libexec/ , I don't use AirPlay nor AirPort so if I delete these two processes will it again screw up my mac the processes are AirPlayXPCHelper and airportd

I don't even use Safari sync nor iCloud so I am thinking of deleting these .plist files /System/Library/LaunchAgents/com.apple.SafariCloudHistoryPushAgent.plist - 'com.apple.SafariCloudHistoryPushAgent'

What happened previously Accidentally deleted a system framework, macOS screwed! while messing with the OS

I am also thinking of running these commands to tweak my Mac


# IMPORTANT: You will need to disable SIP aka Rootless in order to fully execute this script, you can reenable it after.
# WARNING: It might disable things that you may not like. Please double check the services in the TODISABLE vars.

# Get active services: launchctl list | grep -v "\-\t0"
# Find a service: grep -lR [service] /System/Library/Launch* /Library/Launch* ~/Library/LaunchAgents

# Agents to disable
TODISABLE=('com.apple.security.keychainsyncingoveridsproxy' 'com.apple.personad' 'com.apple.passd' 'com.apple.screensharing.MessagesAgent' 'com.apple.CommCenter-osx' 'com.apple.Maps.mapspushd' 'com.apple.Maps.pushdaemon' 'com.apple.photoanalysisd' 'com.apple.telephonyutilities.callservicesd' 'com.apple.AirPlayUIAgent' 'com.apple.AirPortBaseStationAgent' 'com.apple.CalendarAgent' 'com.apple.DictationIM' 'com.apple.iCloudUserNotifications' 'com.apple.familycircled' 'com.apple.familycontrols.useragent' 'com.apple.familynotificationd' 'com.apple.gamed' 'com.apple.icloud.findmydeviced.findmydevice-user-agent' 'com.apple.icloud.fmfd' 'com.apple.imagent' 'com.apple.cloudfamilyrestrictionsd-mac' 'com.apple.cloudpaird' 'com.apple.cloudphotosd' 'com.apple.DictationIM' 'com.apple.assistant_service' 'com.apple.CallHistorySyncHelper' 'com.apple.CallHistoryPluginHelper' 'com.apple.AOSPushRelay' 'com.apple.IMLoggingAgent' 'com.apple.geodMachServiceBridge' 'com.apple.syncdefaultsd' 'com.apple.security.cloudkeychainproxy3' 'com.apple.security.idskeychainsyncingproxy' 'com.apple.security.keychain-circle-notification' 'com.apple.sharingd' 'com.apple.appleseed.seedusaged' 'com.apple.cloudd' 'com.apple.assistantd' 'com.apple.parentalcontrols.check' 'com.apple.parsecd' 'com.apple.identityservicesd')

for agent in "${TODISABLE[@]}"
        sudo launchctl unload -w /System/Library/LaunchAgents/${agent}.plist
        launchctl unload -w /System/Library/LaunchAgents/${agent}.plist
    } &> /dev/null
    sudo mv /System/Library/LaunchAgents/${agent}.plist /System/Library/LaunchAgents/${agent}.plist.bak
    echo "[OK] Agent ${agent} disabled"

# Daemons to disable
TODISABLE=('com.apple.netbiosd' 'com.apple.preferences.timezone.admintool' 'com.apple.preferences.timezone.auto' 'com.apple.remotepairtool' 'com.apple.rpmuxd' 'com.apple.security.FDERecoveryAgent' 'com.apple.icloud.findmydeviced' 'com.apple.findmymacmessenger' 'com.apple.familycontrols' 'com.apple.findmymac' 'com.apple.SubmitDiagInfo' 'com.apple.screensharing' 'com.apple.appleseed.fbahelperd' 'com.apple.apsd' 'com.apple.AOSNotificationOSX' 'com.apple.FileSyncAgent.sshd' 'com.apple.ManagedClient.cloudconfigurationd' 'com.apple.ManagedClient.enroll' 'com.apple.ManagedClient' 'com.apple.ManagedClient.startup' 'com.apple.iCloudStats' 'com.apple.locationd' 'com.apple.mbicloudsetupd' 'com.apple.laterscheduler' 'com.apple.awacsd' 'com.apple.eapolcfg_auth' 'com.apple.familycontrols')

for daemon in "${TODISABLE[@]}"
        sudo launchctl unload -w /System/Library/LaunchDaemons/${daemon}.plist
        launchctl unload -w /System/Library/LaunchDaemons/${daemon}.plist
    } &> /dev/null
    sudo mv /System/Library/LaunchDaemons/${daemon}.plist /System/Library/LaunchDaemons/${daemon}.plist.bak
    echo "[OK] Daemon ${daemon} disabled"
  • Do these processes cause problems with your computer? Just because they provide some service you don't presently utilize doesn't mean they are taking up much disk space or appreciable processing power. Feel free to delete anything you wish, just beware that you may make your computer unusable.
    – IconDaemon
    Oct 3, 2017 at 14:51
  • 1
    @IconDaemon They keep working in the background and can take up to 20% of CPU usage so why keep these processes active when you don't need it!
    – Sayan
    Oct 3, 2017 at 14:54
  • Have you turned them off in system preferences. I have never seen them that high in cpu
    – mmmmmm
    Oct 3, 2017 at 17:29
  • 1
    @Mark I did but still they are active!
    – Sayan
    Oct 3, 2017 at 17:40
  • One-line answer: never delete MacOS system stuff. Learn how to use launchctl to disable/unload launch daemons/agents, whether system, user or gui. At the most, rename the .plist -> .plist.bak, or chmod directories. Never delete.
    – smci
    Jan 14, 2023 at 22:19

1 Answer 1


Be careful!

Deleting the plist files and disabling them are two different things.

Those plists you mentioned in your block quote are (only imho) relatively save to disable on Sierra when SIP is disabled. SIP should probably be re-eanbled after you have finished tweaking your system.

What will be disabled is at first relatively easy to discern when just looking at the names of the culprits. But that can sometimes have quite unwelcome side-effects or unintended consequences.

These background processes are notoriously badly documented. For example: disabling AiplayXPCHelper; that seems wholly superfluous but once disabled iTunes might refuse to even start. Gaining RAM and a few cycles from disabling one process might also be offset by many status and even error messages now written into your logs because certain Apple services try to communicate with others that are presumed to be 'there' but aren't.

A good number of those processes are frankly just absolutely essential and needed for a system to run properly at all. Some can be disabled. So, yes, you can screw up your mac. That last sentence is important.

How to approach disabling features that seem unnecessary or are decidedly unwanted was described for example here.

Have I said be careful yet? You have been warned.

Document your steps. Proceed slowly. Backup even more frequently than before. Be sure you are able to retrace your steps. Keep two different backups and a bootable installer handy.

Therefore: deleting those plist files seems more thorough than just disabling them. Any space gained on disk is surely not worth it. But disabling is just so much easier to revert in case something goes wrong.

After reminding you to be careful once more: just do not delete things from /usr/libexec !

  • One more thing I have turbo booster installed on my mac so it keeps my CPU running at it's highest capacity(.i.e when turbo boosted) so while this app was running and since I have a dual core processor I ran this command two times in two separate windows commands: yes>/dev/null and since I have ran these commands the CPU consumption was 100% and since then I am facing lags across the OS, I also have smc fancontrol running the Fans always at 2880 rpm, should I be concerned about this since the OS is a little laggy frame rate wise
    – Sayan
    Oct 4, 2017 at 12:48
  • You should killall yes processes. Or reboot. Runnig yes permanently is no good idea at all. Oct 4, 2017 at 12:52
  • I ran yes>/dev/null command for 5 mins so did it harm my mac?
    – Sayan
    Oct 4, 2017 at 13:15
  • As discussed in apple.stackexchange.com/q/295250/251859 this might be detrimental only under special circumstances. But very probably not and not at 5 minutes. It's just a waste of electricity and performance, as you may have noticed. Oct 4, 2017 at 13:18

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .