How to remove constantly launching services on Mac OS X
Even after you uninstall it, some Mac OS X software just won’t quit nagging you or notifying you of updates or at the very least polluting the Console Messages like this:
Code
19/08/11 00:16:46 com.apple.launchd.peruser.501[689] (com.carbonite.carbonitestatus[14428]) posix_spawn("/Library/Application Support/Carbonite/CarboniteStatus.app/Contents/MacOS/CarboniteStatus", ...): No such file or directory | |
19/08/11 00:16:46 com.apple.launchd.peruser.501[689] (com.carbonite.carbonitestatus[14428]) Exited with exit code: 1 | |
19/08/11 00:16:46 com.apple.launchd.peruser.501[689] (com.carbonite.carbonitestatus) Throttling respawn: Will start in 10 seconds | |
19/08/11 00:16:56 com.apple.launchd.peruser.501[689] (com.carbonite.carbonitestatus[14437]) posix_spawn("/Library/Application Support/Carbonite/CarboniteStatus.app/Contents/MacOS/CarboniteStatus", ...): No such file or directory | |
19/08/11 00:16:56 com.apple.launchd.peruser.501[689] (com.carbonite.carbonitestatus[14437]) Exited with exit code: 1 | |
19/08/11 00:16:56 com.apple.launchd.peruser.501[689] (com.carbonite.carbonitestatus) Throttling respawn: Will start in 10 seconds |
Well here’s how you kill those constantly launching things!
Open a Terminal window and enter launchctl list to see a list of all launching services. Once you know what you want to kill, use launchctl remove.
Here is an example on that pesky Carbonite:
Code
macpro$ launchctl list | grep carbonite | |
- 1 com.carbonite.carbonitestatus | |
- 0 com.carbonite.carbonitealerts | |
macpro$ launchctl remove com.carbonite.carbonitestatus | |
macpro$ launchctl remove com.carbonite.carbonitealerts |
Here is another on Intego backup:
Code
macpro$ launchctl list | grep intego | |
- 0 com.intego.backupmanagerpro.agent | |
macpro$ launchctl remove com.intego.backupmanagerpro.agent |
This entry was posted on August 19th, 2011 at 00:30 by admin and is filed under Mac stuff. Tags: howto, mac os x, terminal
This entry was posted on 19. August 2011 by François Planque and is filed under Mac stuff. Tags: howto, mac os x, terminal
This is the best solution I found in the web.
I was having this problem and it was annoying. my MBP won’t go to sleep mode even if i close the lid.
you are a life saver,
Sorry for bad english.
best regards,
sulaiman
and what if I were just to navigate to the folder in User/homeƒolder/library/LaunchAgents
and delete the offending files from there?
would that still leave orphaned files on my hard drive?
thanks for the Terminal script btw,these 10 sec respawns have been driving me nuts
Just adding my thanks to those above. Great instructions. Clear. Easy to follow. And effective.
Great instruction. Just what I needed. Thanks!
how the heck do i turn off any and all postfix services to stop all the postfix errors that have been compiling for years – since I don’t use postifx, have no idea how to use it and it’s constantly creating errors in my log?
thank you sincerely!
I’ve been trying to find a solution to removing a ‘MacKeeper’ file for three weeks, thank you…
This solution worked great!!!
Thanks! It took me a really long time to understand what was going on!
specifically type “launchctl remove” and then what? Just typing that gets the message command not found. I put in the line number where the carbonite code is and copied and pasted the code after typing “launchctl remove". PLEASE BE MORE EXPLICIT WITH DIRECTIONS. Thanks
I’m pretty sure you need to use “sudo” for launchctl to even see system launch agents. Otherwise it just looks for stuff from your user.
Unless of course you’re just looking for launch agents that are in your user account.
excellent solution… hopefully it sticks. i tried something else to stop notification center from launching (after I disabled it the wrong way) and the messages came back. worst case, i’ll have to enter the commands every time the computer starts up, which i really don’t mind. THANK YOU!!!!!
Great! Very helpful to get rid of annoying scripts that fail
yes, launchctl remove worked for zeobit, but on the restart it came back. Suggestions?
hi i need an information this solution is to remove constantly launching services on Mac OS X but to remove the file definitive???
Thanks
I tried the Terminal launchctl remove for a constant problem with throttling respawn of a mobile broadband manager, but it didn’t work - just keeps on running and running every 10 seconds, slowing down my computer. Any other suggestions please?
THANK YOU! Worked like a charm on this stupid Mobilegodaemon that’s been plaguing me for months.
awesome. I love you, too. After digging through gloogle for hours, finally an answer, short and simple. You rock!
I discovered I had two of the damn things on my box, maybe this will help someone;
4/19/15 4:41:06 PM com.apple.launchd[1] (com.daz3d.content_management_service[4695]) Exited with exit code: 1
4/19/15 4:41:06 PM com.apple.launchd[1] (com.daz3d.content_management_service) Throttling respawn: Will start in 10 seconds
4/19/15 4:41:06 PM com.apple.launchd[1] (com.zeobit.MacKeeper.plugin.AntiTheft.daemon[4696]) posix_spawn("/Library/Application Support/MacKeeper/MacKeeperATd", …): No such file or directory
I used the list command shown here, and easily removed the 2nd one, the zeobit.mackeeper garbage, but the DAZ did not show up at all in the list, not even when I used sudo;
sudo launchctl list
So on a hunch I figured it was somehow hidden, so I tried this syntax and the console logging immediately STOPPED;
sudo launchctl remove com.daz3d.content_management_service
Tried your string to get rid of the wondershare problem no such luck!
Any solutions for the following messages constantly showing in Console (Mac OS 10.8)
18/01/2016 14:38:30.771 com.apple.launchd.peruser.501[257]: (com.wondershare.mobilegodaemon[3834]) Job failed to exec(3) for weird reason: 13
18/01/2016 14:38:30.771 com.apple.launchd.peruser.501[257]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds
18/01/2016 14:38:40.773 com.apple.launchd.peruser.501[257]: (com.wondershare.mobilegodaemon[3835]) Job failed to exec(3) for weird reason: 13
18/01/2016 14:38:40.773 com.apple.launchd.peruser.501[257]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds
18/01/2016 14:38:50.775 com.apple.launchd.peruser.501[257]: (com.wondershare.mobilegodaemon[3842]) Job failed to exec(3) for weird reason: 13
18/01/2016 14:38:50.775 com.apple.launchd.peruser.501[257]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds
18/01/2016 14:39:00.777 com.apple.launchd.peruser.501[257]: (com.wondershare.mobilegodaemon[3845]) Job failed to exec(3) for weird reason: 13
18/01/2016 14:39:00.777 com.apple.launchd.peruser.501[257]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds
18/01/2016 14:39:10.779 com.apple.launchd.peruser.501[257]: (com.wondershare.mobilegodaemon[3850]) Job failed to exec(3) for weird reason: 13
18/01/2016 14:39:10.779 com.apple.launchd.peruser.501[257]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds
18/01/2016 14:39:20.781 com.apple.launchd.peruser.501[257]: (com.wondershare.mobilegodaemon[3853]) Job failed to exec(3) for weird reason: 13
18/01/2016 14:39:20.781 com.apple.launchd.peruser.501[257]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds
three and a half years later, your fix still is findable on google, and still works! thanks so much. –mike
Form is loading...
