![]() Use Terminal: this may be the preferred method for advanced Mac users, but it's easy to get used to once you have got the taste for working with Terminal.Launch Activity Monitor if you haven't already done so and, in the CPU tab, select the process that is using most of the processor's resources and click the “Quit Process” button. Use Activity Monitor: if you keep an eye on your Mac's resource hog, Activity Monitor is the best tool to spot unresponsive apps and quit them.This isn’t the most effective method, however, as unresponsive apps may have inaccessible menus. From the Apple menu: hold down the Shift key while clicking on the Apple menu, and you'll see “Force Quit in the drop down menu.Use the Option + Right Click trick on the targeted app's dock icon to bring up the “Force Quit” option, and select it to kill the app.Drag this action and drop it onto the gray pane on the right. An action named Quit All Applications will appear beneath the text box. Then, click the text box next to Actions and type Quit All Applications. You might need to hold down those keys for a second or two. Then, click Choose at the bottom of the pop-up. An advanced version of the key combination without bringing up the aforementioned window: hit Command + Option + Shift + Escape.Use a keyboard shortcut: hit Command + Option + Escape to bring up the “Force Quit Applications” window, and select the faulty app.Six Ways to Quit an App in Any Version of macOS That option disappears when you force the app to quit, similar to choosing “End Task” in the Control Panel after pressing Control + Alt + Delete on a PC. A normal closure of the app will display a prompt (if needed) to save any changes you have made and will quit only after answering this prompt. To quit (close) the app, you simply need to press Command + Q to choose Quit from the app's menu in the menu bar. (The $(date) in the echo is because this runs in the background at startup based on wifi connections and the output goes to a log file.)Īpologies if I'm not answering the "right way" as this is my first post.Force Quit is usually used to close an app that has stopped responding completely and prevents quitting the app normally. *) echo "$(date): Bad call of function GoogleDrive"Įcho "$(date): GoogleDrive " # Actually stop all users if we found any that are running, otherwise just say they are all stoppedĮcho "$(date): No Google Backup and Sync Processes were running" If ps -p $pidtokill | grep "Backup\ and\ Sync"> /dev/nullĮcho "$(date): Stopping backup and Sync for user $user"Įcho "$(date): Google Backup and Sync user $user is not running" Pidtokill=$(cat $HOME/Library/Application\ Support/Google/Drive/$dirname/pid) Also don't know what the results of the osascript call is when there are multiple users.įunction GoogleBackup ' | sed 's///g') I have a script to do that, but I don't have multiple users anymore, so not sure it still works, but for what it's worth it's below. Note that if you have multiple users configured in Backup and Sync, you'll have to figure out the PID of the correct user, and then kill it. Osascript -e 'quit app "Backup and Sync"' Find the app that’s frozen, and take note of the PID number shown to the left of the app. 3) Terminal will now show you a list of processes running on your Mac. 2) Type in the following command, then hit the Return key on your keyboard: ps -ax. Osascript -e 'tell application "Backup and Sync" to activate' To force quit an app with Terminal, follow these steps: 1) Launch the Terminal app on your Mac. This is ALSO what osascript also knows it as, so you can do: "Backup and Sync from Google" is just branding. In fact, if you look in the applications directory with finder and do a "get info" it will show you the real application name. It shows that the process name has no "from Google" in it. If you do:ĥ01 37327 1 0 3:37PM ? 0:06.37 /Applications/Backup and Sync.app/Contents/MacOS/Backup and Sync The reason the "\ from\ Google" doesn't work is because that is not what the process is, there is no "from Google in the process name. ![]() This post is old, but I struggled with it, so I thought I'd help.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |