Take the 2-minute tour ×
Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.

It happens to me that, sometimes, the MobileMe synchronization starts when it should not, when Mac OS X is busy doing something time-consuming. In such cases, I try to stop the synchronization using its menu extra, but for some reasons the synchronization doesn't stop.
Is there a way to stop it from Terminal?

share|improve this question
    
I find it best to disconnect from the network (which is doable by taking down the active interfaces or modifying the routing tables) and then letting the sync time out. You can then disable it. This might be of use to people that don't want to killall in terminal. –  bmike Jun 9 '11 at 16:53
add comment

1 Answer

up vote 1 down vote accepted

Try this :

sudo kill -9 /System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/Resources/mobilemesyncclient

I don't use Mobile Me so cannot test this but this is the location of the Mobile Me sync command. So killing it should stop the syncing.

share|improve this answer
    
The command returns the error "Illegal process ID." –  kiamlaluno Apr 22 '11 at 11:30
    
yes, it will when the Sync command is not running. Did you try running the command whilst it was syncing? –  RobZolkos Apr 22 '11 at 11:35
    
I tried it when the synchronization was running, but in two different Macs I got the following error message: "-bash: kill: /System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/Resourc‌​es/mobilemesyncclient: arguments must be process or job IDs". –  kiamlaluno Apr 22 '11 at 12:37
    
I tried "killall −9 mobilemesyncclient," and it worked. –  kiamlaluno Apr 22 '11 at 12:39
    
ah cool. Glad you figured it out ;) –  RobZolkos Apr 22 '11 at 12:46
show 1 more 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.