How can I quit an app using Terminal? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern) Should an RSS feed of hot network questions feed any chat room(s) here?Can home and end keys be mapped when using Terminal?Bash Script that will start up second Terminal process?How do I kill a process that won't die?How do I programatically kill the CCLibrary process by PID?How does one start a bash command that doesn't close on Terminal quit?Quit terminal but store the session for next startHow to Programmatically Find, Kill, and Restart a local DynamoDB ProcessHow to switch focus to the app based on its PID from CLI?How to set a fixed title for a terminal in Mac?How can I open an app using Terminal?

How to react to hostile behavior from a senior developer?

Take 2! Is this homebrew Lady of Pain warlock patron balanced?

Drawing without replacement: why is the order of draw irrelevant?

What do you call the main part of a joke?

A term for a woman complaining about things/begging in a cute/childish way

What would you call this weird metallic apparatus that allows you to lift people?

Can a new player join a group only when a new campaign starts?

Why do we bend a book to keep it straight?

Why is it faster to reheat something than it is to cook it?

What does it mean that physics no longer uses mechanical models to describe phenomena?

How do I use the new nonlinear finite element in Mathematica 12 for this equation?

Sum letters are not two different

What is the topology associated with the algebras for the ultrafilter monad?

How fail-safe is nr as stop bytes?

Maximum summed subsequences with non-adjacent items

Why weren't discrete x86 CPUs ever used in game hardware?

What is the font for "b" letter?

As a beginner, should I get a Squier Strat with a SSS config or a HSS?

How would a mousetrap for use in space work?

Using audio cues to encourage good posture

Why is Nikon 1.4g better when Nikon 1.8g is sharper?

If Windows 7 doesn't support WSL, then what does Linux subsystem option mean?

Can the Great Weapon Master feat's "Power Attack" apply to attacks from the Spiritual Weapon spell?

Effects on objects due to a brief relocation of massive amounts of mass

How can I quit an app using Terminal?

Announcing the arrival of Valued Associate #679: Cesar Manara

Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)

Should an RSS feed of hot network questions feed any chat room(s) here?Can home and end keys be mapped when using Terminal?Bash Script that will start up second Terminal process?How do I kill a process that won't die?How do I programatically kill the CCLibrary process by PID?How does one start a bash command that doesn't close on Terminal quit?Quit terminal but store the session for next startHow to Programmatically Find, Kill, and Restart a local DynamoDB ProcessHow to switch focus to the app based on its PID from CLI?How to set a fixed title for a terminal in Mac?How can I open an app using Terminal?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

I want to quit a certain applications on my Mac using Terminal. For example, how do I kill “Slack”? Do I need its PID number?

edited Mar 29 at 1:23

bmike♦

162k46292633

asked Mar 27 at 14:15

Brainmaniac

28219

add a comment |

I want to quit a certain applications on my Mac using Terminal. For example, how do I kill “Slack”? Do I need its PID number?

edited Mar 29 at 1:23

bmike♦

162k46292633

asked Mar 27 at 14:15

Brainmaniac

28219

add a comment |

I want to quit a certain applications on my Mac using Terminal. For example, how do I kill “Slack”? Do I need its PID number?

edited Mar 29 at 1:23

bmike♦

162k46292633

asked Mar 27 at 14:15

Brainmaniac

28219

I want to quit a certain applications on my Mac using Terminal. For example, how do I kill “Slack”? Do I need its PID number?

macos terminal command-line

edited Mar 29 at 1:23

bmike♦

162k46292633

asked Mar 27 at 14:15

Brainmaniac

28219

edited Mar 29 at 1:23

bmike♦

162k46292633

asked Mar 27 at 14:15

Brainmaniac

28219

edited Mar 29 at 1:23

bmike♦

162k46292633

edited Mar 29 at 1:23

bmike♦

162k46292633

edited Mar 29 at 1:23

bmike♦

162k46292633

asked Mar 27 at 14:15

Brainmaniac

28219

asked Mar 27 at 14:15

Brainmaniac

28219

asked Mar 27 at 14:15

Brainmaniac

28219

add a comment |

5 Answers
5

active

oldest

votes

No, you do not need to know its PID.

You can use:

pkill -x Slack

Or:

killall Slack

Note: Be sure to read the manual page for whichever command you choose to use, in order to see the various options available to the command, as may be relevant to its particular usage. In Terminal type e.g. man pkill and press enter, or just type the command and right-click on it, then select: Open man Page

edited Mar 29 at 0:50

answered Mar 27 at 14:26

user3439894

28.9k64666

add a comment |

You can use AppleScript to tell the application to quit:

osascript -e 'quit app "Slack"'

this will tell the application to quit and will start all the save and cleanup tasks. Or you can send the TERM signal with pkill but it could be that the application will not shut down cleanly

pkill -x Slack

edited Mar 28 at 21:17

answered Mar 28 at 6:52

Matteo

5,372135599

7

This is the best method, because it replicates what happens when you use File>Quit from the menu.

– Barmar
Mar 28 at 16:15

2

Huh. I've always used osascript -e 'tell application "Slack" to quit' but if the shorter syntax works, then that's obviously preferable. This is definitely a better answer than anything suggesting kill or any of its variants.

– TJ Luoma
Mar 30 at 2:58

@TJLuoma I think if you select the correct signal, then pkill is as graceful as any other method. I too favour the AppleScript, though created a function quit to make it breezy. However, if creating an AppleScript process isn’t necessary, pkill -QUIT -x Slack should be fine.

– CJK
yesterday

add a comment |

Since I don't yet have the reputation to comment, I'm saying this as a separate answer. pkill without any flags does not match a specific process! For example, running pkill foo would target processes named foo, but would also target processes named foobar. This is because it uses regular expressions.

If you wish to kill a specific process, you can pass it the -x flag. For example, pkill -x foo. This will use exact names instead of regular expressions.

For example, in your case, pkill -x Slack will do the trick.

edited Mar 29 at 21:36

answered Mar 27 at 21:59

user321134

1335

To turn this into a full answer can you please add the name of the Slack process to kill?

– nohillside♦
Mar 29 at 16:48

add a comment |

You can install htop (via brew for instance).

You'll need to run this as root or with sudo. Essentially, it's a text
based Activity Monitor.

Select the process you want to kill (either with arrow keys or a mouse).

Then press k to send the process a signal and then 9 to choose the SIGKILL signal.

edited Mar 29 at 0:42

Dancrumb

1255

answered Mar 27 at 17:20

BEFio

811

We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.

add a comment |

I'm not sure for Slack, but some Applications will run multiple Processes and you may want to kill just one (I find I often need to do this with iTunes, for example). In that case, you can run

ps -e | grep -i slack

To find all Processes with case-insensitive "slack" in the name. The output should look like (without the header):

PID TTY TIME CMD
649 pts/1 00:00:00 bash

That first column will be your PID. You can then use that to kill specifically that process:

kill -9 649

Replacing 649 with your PID you found from calling ps.

answered Mar 27 at 18:57

scohe001

35239

2

kill sends a signal to terminate the app. It is not necessary to use -9 (kill) if the application is responding. You risk to loose unsaved data

– Matteo
Mar 28 at 17:58

Similarly, if you did happen to want to kill, say, all 5 instances of some named process, you could filter the output of ps on the CMD value and then kill all the first entries on those lines.

– Carl Witthoft
Mar 29 at 14:59

1

@Carl Witthoft, you can simply use killall procname, e.g. killall Slack and it will kill all occurrences of Slack or whatever procname is. No need to use ps!

– user3439894
Mar 29 at 22:26

So, pgrep is a nice command that combines ps and grip.

– Harv
Apr 3 at 0:47

add a comment |

5 Answers
5

active

oldest

votes

5 Answers
5

active

oldest

votes

No, you do not need to know its PID.

You can use:

pkill -x Slack

Or:

killall Slack

edited Mar 29 at 0:50

answered Mar 27 at 14:26

user3439894

28.9k64666

add a comment |

No, you do not need to know its PID.

You can use:

pkill -x Slack

Or:

killall Slack

edited Mar 29 at 0:50

answered Mar 27 at 14:26

user3439894

28.9k64666

add a comment |

No, you do not need to know its PID.

You can use:

pkill -x Slack

Or:

killall Slack

edited Mar 29 at 0:50

answered Mar 27 at 14:26

user3439894

28.9k64666

No, you do not need to know its PID.

You can use:

pkill -x Slack

Or:

killall Slack

edited Mar 29 at 0:50

answered Mar 27 at 14:26

user3439894

28.9k64666

edited Mar 29 at 0:50

answered Mar 27 at 14:26

user3439894

28.9k64666

answered Mar 27 at 14:26

user3439894

28.9k64666

answered Mar 27 at 14:26

user3439894

28.9k64666

add a comment |

You can use AppleScript to tell the application to quit:

osascript -e 'quit app "Slack"'

this will tell the application to quit and will start all the save and cleanup tasks. Or you can send the TERM signal with pkill but it could be that the application will not shut down cleanly

pkill -x Slack

edited Mar 28 at 21:17

answered Mar 28 at 6:52

Matteo

5,372135599

7

This is the best method, because it replicates what happens when you use File>Quit from the menu.

– Barmar
Mar 28 at 16:15

2

Huh. I've always used osascript -e 'tell application "Slack" to quit' but if the shorter syntax works, then that's obviously preferable. This is definitely a better answer than anything suggesting kill or any of its variants.

– TJ Luoma
Mar 30 at 2:58

@TJLuoma I think if you select the correct signal, then pkill is as graceful as any other method. I too favour the AppleScript, though created a function quit to make it breezy. However, if creating an AppleScript process isn’t necessary, pkill -QUIT -x Slack should be fine.

– CJK
yesterday

add a comment |

You can use AppleScript to tell the application to quit:

osascript -e 'quit app "Slack"'

this will tell the application to quit and will start all the save and cleanup tasks. Or you can send the TERM signal with pkill but it could be that the application will not shut down cleanly

pkill -x Slack

edited Mar 28 at 21:17

answered Mar 28 at 6:52

Matteo

5,372135599

7

This is the best method, because it replicates what happens when you use File>Quit from the menu.

– Barmar
Mar 28 at 16:15

2

Huh. I've always used osascript -e 'tell application "Slack" to quit' but if the shorter syntax works, then that's obviously preferable. This is definitely a better answer than anything suggesting kill or any of its variants.

– TJ Luoma
Mar 30 at 2:58

@TJLuoma I think if you select the correct signal, then pkill is as graceful as any other method. I too favour the AppleScript, though created a function quit to make it breezy. However, if creating an AppleScript process isn’t necessary, pkill -QUIT -x Slack should be fine.

– CJK
yesterday

add a comment |

You can use AppleScript to tell the application to quit:

osascript -e 'quit app "Slack"'

this will tell the application to quit and will start all the save and cleanup tasks. Or you can send the TERM signal with pkill but it could be that the application will not shut down cleanly

pkill -x Slack

edited Mar 28 at 21:17

answered Mar 28 at 6:52

Matteo

5,372135599

You can use AppleScript to tell the application to quit:

osascript -e 'quit app "Slack"'

this will tell the application to quit and will start all the save and cleanup tasks. Or you can send the TERM signal with pkill but it could be that the application will not shut down cleanly

pkill -x Slack

edited Mar 28 at 21:17

answered Mar 28 at 6:52

Matteo

5,372135599

edited Mar 28 at 21:17

answered Mar 28 at 6:52

Matteo

5,372135599

answered Mar 28 at 6:52

Matteo

5,372135599

answered Mar 28 at 6:52

Matteo

5,372135599

7

This is the best method, because it replicates what happens when you use File>Quit from the menu.

– Barmar
Mar 28 at 16:15

2

Huh. I've always used osascript -e 'tell application "Slack" to quit' but if the shorter syntax works, then that's obviously preferable. This is definitely a better answer than anything suggesting kill or any of its variants.

– TJ Luoma
Mar 30 at 2:58

@TJLuoma I think if you select the correct signal, then pkill is as graceful as any other method. I too favour the AppleScript, though created a function quit to make it breezy. However, if creating an AppleScript process isn’t necessary, pkill -QUIT -x Slack should be fine.

– CJK
yesterday

add a comment |

7

This is the best method, because it replicates what happens when you use File>Quit from the menu.

– Barmar
Mar 28 at 16:15

2

Huh. I've always used osascript -e 'tell application "Slack" to quit' but if the shorter syntax works, then that's obviously preferable. This is definitely a better answer than anything suggesting kill or any of its variants.

– TJ Luoma
Mar 30 at 2:58

@TJLuoma I think if you select the correct signal, then pkill is as graceful as any other method. I too favour the AppleScript, though created a function quit to make it breezy. However, if creating an AppleScript process isn’t necessary, pkill -QUIT -x Slack should be fine.

– CJK
yesterday

This is the best method, because it replicates what happens when you use File>Quit from the menu.

– Barmar
Mar 28 at 16:15

Huh. I've always used osascript -e 'tell application "Slack" to quit' but if the shorter syntax works, then that's obviously preferable. This is definitely a better answer than anything suggesting kill or any of its variants.

– TJ Luoma
Mar 30 at 2:58

@TJLuoma I think if you select the correct signal, then pkill is as graceful as any other method. I too favour the AppleScript, though created a function quit to make it breezy. However, if creating an AppleScript process isn’t necessary, pkill -QUIT -x Slack should be fine.

– CJK
yesterday

add a comment |

If you wish to kill a specific process, you can pass it the -x flag. For example, pkill -x foo. This will use exact names instead of regular expressions.

For example, in your case, pkill -x Slack will do the trick.

edited Mar 29 at 21:36

answered Mar 27 at 21:59

user321134

1335

To turn this into a full answer can you please add the name of the Slack process to kill?

– nohillside♦
Mar 29 at 16:48

add a comment |

If you wish to kill a specific process, you can pass it the -x flag. For example, pkill -x foo. This will use exact names instead of regular expressions.

For example, in your case, pkill -x Slack will do the trick.

edited Mar 29 at 21:36

answered Mar 27 at 21:59

user321134

1335

To turn this into a full answer can you please add the name of the Slack process to kill?

– nohillside♦
Mar 29 at 16:48

add a comment |

If you wish to kill a specific process, you can pass it the -x flag. For example, pkill -x foo. This will use exact names instead of regular expressions.

For example, in your case, pkill -x Slack will do the trick.

edited Mar 29 at 21:36

answered Mar 27 at 21:59

user321134

1335

If you wish to kill a specific process, you can pass it the -x flag. For example, pkill -x foo. This will use exact names instead of regular expressions.

For example, in your case, pkill -x Slack will do the trick.

edited Mar 29 at 21:36

answered Mar 27 at 21:59

user321134

1335

edited Mar 29 at 21:36

answered Mar 27 at 21:59

user321134

1335

answered Mar 27 at 21:59

user321134

1335

answered Mar 27 at 21:59

user321134

1335

To turn this into a full answer can you please add the name of the Slack process to kill?

– nohillside♦
Mar 29 at 16:48

add a comment |

To turn this into a full answer can you please add the name of the Slack process to kill?

– nohillside♦
Mar 29 at 16:48

To turn this into a full answer can you please add the name of the Slack process to kill?

– nohillside♦
Mar 29 at 16:48

add a comment |

You can install htop (via brew for instance).

You'll need to run this as root or with sudo. Essentially, it's a text
based Activity Monitor.

Select the process you want to kill (either with arrow keys or a mouse).

Then press k to send the process a signal and then 9 to choose the SIGKILL signal.

edited Mar 29 at 0:42

Dancrumb

1255

answered Mar 27 at 17:20

BEFio

811

add a comment |

You can install htop (via brew for instance).

You'll need to run this as root or with sudo. Essentially, it's a text
based Activity Monitor.

Select the process you want to kill (either with arrow keys or a mouse).

Then press k to send the process a signal and then 9 to choose the SIGKILL signal.

edited Mar 29 at 0:42

Dancrumb

1255

answered Mar 27 at 17:20

BEFio

811

add a comment |

You can install htop (via brew for instance).

You'll need to run this as root or with sudo. Essentially, it's a text
based Activity Monitor.

Select the process you want to kill (either with arrow keys or a mouse).

Then press k to send the process a signal and then 9 to choose the SIGKILL signal.

edited Mar 29 at 0:42

Dancrumb

1255

answered Mar 27 at 17:20

BEFio

811

You can install htop (via brew for instance).

You'll need to run this as root or with sudo. Essentially, it's a text
based Activity Monitor.

Select the process you want to kill (either with arrow keys or a mouse).

Then press k to send the process a signal and then 9 to choose the SIGKILL signal.

edited Mar 29 at 0:42

Dancrumb

1255

answered Mar 27 at 17:20

BEFio

811

edited Mar 29 at 0:42

Dancrumb

1255

edited Mar 29 at 0:42

Dancrumb

1255

edited Mar 29 at 0:42

Dancrumb

1255

answered Mar 27 at 17:20

BEFio

811

answered Mar 27 at 17:20

BEFio

811

answered Mar 27 at 17:20

BEFio

811

add a comment |

I'm not sure for Slack, but some Applications will run multiple Processes and you may want to kill just one (I find I often need to do this with iTunes, for example). In that case, you can run

ps -e | grep -i slack

To find all Processes with case-insensitive "slack" in the name. The output should look like (without the header):

PID TTY TIME CMD
649 pts/1 00:00:00 bash

That first column will be your PID. You can then use that to kill specifically that process:

kill -9 649

Replacing 649 with your PID you found from calling ps.

answered Mar 27 at 18:57

scohe001

35239

2

kill sends a signal to terminate the app. It is not necessary to use -9 (kill) if the application is responding. You risk to loose unsaved data

– Matteo
Mar 28 at 17:58

Similarly, if you did happen to want to kill, say, all 5 instances of some named process, you could filter the output of ps on the CMD value and then kill all the first entries on those lines.

– Carl Witthoft
Mar 29 at 14:59

1

@Carl Witthoft, you can simply use killall procname, e.g. killall Slack and it will kill all occurrences of Slack or whatever procname is. No need to use ps!

– user3439894
Mar 29 at 22:26

So, pgrep is a nice command that combines ps and grip.

– Harv
Apr 3 at 0:47

add a comment |

I'm not sure for Slack, but some Applications will run multiple Processes and you may want to kill just one (I find I often need to do this with iTunes, for example). In that case, you can run

ps -e | grep -i slack

To find all Processes with case-insensitive "slack" in the name. The output should look like (without the header):

PID TTY TIME CMD
649 pts/1 00:00:00 bash

That first column will be your PID. You can then use that to kill specifically that process:

kill -9 649

Replacing 649 with your PID you found from calling ps.

answered Mar 27 at 18:57

scohe001

35239

2

kill sends a signal to terminate the app. It is not necessary to use -9 (kill) if the application is responding. You risk to loose unsaved data

– Matteo
Mar 28 at 17:58

Similarly, if you did happen to want to kill, say, all 5 instances of some named process, you could filter the output of ps on the CMD value and then kill all the first entries on those lines.

– Carl Witthoft
Mar 29 at 14:59

1

@Carl Witthoft, you can simply use killall procname, e.g. killall Slack and it will kill all occurrences of Slack or whatever procname is. No need to use ps!

– user3439894
Mar 29 at 22:26

So, pgrep is a nice command that combines ps and grip.

– Harv
Apr 3 at 0:47

add a comment |

I'm not sure for Slack, but some Applications will run multiple Processes and you may want to kill just one (I find I often need to do this with iTunes, for example). In that case, you can run

ps -e | grep -i slack

To find all Processes with case-insensitive "slack" in the name. The output should look like (without the header):

PID TTY TIME CMD
649 pts/1 00:00:00 bash

That first column will be your PID. You can then use that to kill specifically that process:

kill -9 649

Replacing 649 with your PID you found from calling ps.

answered Mar 27 at 18:57

scohe001

35239

I'm not sure for Slack, but some Applications will run multiple Processes and you may want to kill just one (I find I often need to do this with iTunes, for example). In that case, you can run

ps -e | grep -i slack

To find all Processes with case-insensitive "slack" in the name. The output should look like (without the header):

PID TTY TIME CMD
649 pts/1 00:00:00 bash

That first column will be your PID. You can then use that to kill specifically that process:

kill -9 649

Replacing 649 with your PID you found from calling ps.

answered Mar 27 at 18:57

scohe001

35239

answered Mar 27 at 18:57

scohe001

35239

answered Mar 27 at 18:57

scohe001

35239

answered Mar 27 at 18:57

scohe001

35239

2

kill sends a signal to terminate the app. It is not necessary to use -9 (kill) if the application is responding. You risk to loose unsaved data

– Matteo
Mar 28 at 17:58

Similarly, if you did happen to want to kill, say, all 5 instances of some named process, you could filter the output of ps on the CMD value and then kill all the first entries on those lines.

– Carl Witthoft
Mar 29 at 14:59

1

@Carl Witthoft, you can simply use killall procname, e.g. killall Slack and it will kill all occurrences of Slack or whatever procname is. No need to use ps!

– user3439894
Mar 29 at 22:26

So, pgrep is a nice command that combines ps and grip.

– Harv
Apr 3 at 0:47

add a comment |

2

kill sends a signal to terminate the app. It is not necessary to use -9 (kill) if the application is responding. You risk to loose unsaved data

– Matteo
Mar 28 at 17:58

Similarly, if you did happen to want to kill, say, all 5 instances of some named process, you could filter the output of ps on the CMD value and then kill all the first entries on those lines.

– Carl Witthoft
Mar 29 at 14:59

1

@Carl Witthoft, you can simply use killall procname, e.g. killall Slack and it will kill all occurrences of Slack or whatever procname is. No need to use ps!

– user3439894
Mar 29 at 22:26

So, pgrep is a nice command that combines ps and grip.

– Harv
Apr 3 at 0:47

kill sends a signal to terminate the app. It is not necessary to use -9 (kill) if the application is responding. You risk to loose unsaved data

– Matteo
Mar 28 at 17:58

Similarly, if you did happen to want to kill, say, all 5 instances of some named process, you could filter the output of ps on the CMD value and then kill all the first entries on those lines.

– Carl Witthoft
Mar 29 at 14:59

@Carl Witthoft, you can simply use killall procname, e.g. killall Slack and it will kill all occurrences of Slack or whatever procname is. No need to use ps!

– user3439894
Mar 29 at 22:26

So, pgrep is a nice command that combines ps and grip.

– Harv
Apr 3 at 0:47

add a comment |

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Fdtxjr

5 Answers
5

5 Answers
5

5 Answers
5

Popular posts from this blog

Daza language Contents Vocabulary Phonology References External links Navigation menudaza1242Daza"Dazaga"eeee178086576

5 Answers 5

5 Answers 5

5 Answers 5

Popular posts from this blog

Daza language Contents Vocabulary Phonology References External links Navigation menudaza1242Daza"Dazaga"eeee178086576

5 Answers
5

5 Answers
5

5 Answers
5