How can I quit an app using Terminal?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?
Is it important to consider tone, melody, and musical form while writing a song?
How do we improve the relationship with a client software team that performs poorly and is becoming less collaborative?
Finding angle with pure Geometry.
Is a tag line useful on a cover?
What is the word for reserving something for yourself before others do?
String Manipulation Interpreter
Is it possible to do 50 km distance without any previous training?
tikz: show 0 at the axis origin
What's the point of deactivating Num Lock on login screens?
I'm planning on buying a laser printer but concerned about the life cycle of toner in the machine
How can I make my BBEG immortal short of making them a Lich or Vampire?
Why Is Death Allowed In the Matrix?
Fencing style for blades that can attack from a distance
How can bays and straits be determined in a procedurally generated map?
What do the dots in this tr command do: tr .............A-Z A-ZA-Z <<< "JVPQBOV" (with 13 dots)
Voyeurism but not really
Font hinting is lost in Chrome-like browsers (for some languages )
What defenses are there against being summoned by the Gate spell?
What do "features" mean/refer to in this sentence?
TGV timetables / schedules?
How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?
Minkowski space
Test whether all array elements are factors of a number
Is it legal for company to use my work email to pretend I still work there?
How can I quit an app using Terminal?
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?
macos terminal command-line
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?
macos terminal command-line
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?
macos terminal command-line
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
macos terminal command-line
edited Mar 29 at 1:23
bmike♦
161k46290628
161k46290628
asked Mar 27 at 14:15
BrainmaniacBrainmaniac
27718
27718
add a comment |
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
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
6
This is the best method, because it replicates what happens when you useFile>Quit
from the menu.
– Barmar
Mar 28 at 16:15
2
Huh. I've always usedosascript -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 suggestingkill
or any of its variants.
– TJ Luoma
Mar 30 at 2:58
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.
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.
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
.
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 ofps
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 usekillall procname
, e.g.killall Slack
and it will kill all occurrences of Slack or whateverprocname
is. No need to useps
!
– user3439894
Mar 29 at 22:26
So,pgrep
is a nice command that combinesps
andgrip
.
– Harv
Apr 3 at 0:47
add a comment |
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
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
add a comment |
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
add a comment |
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
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
user3439894user3439894
28.6k64665
28.6k64665
add a comment |
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
6
This is the best method, because it replicates what happens when you useFile>Quit
from the menu.
– Barmar
Mar 28 at 16:15
2
Huh. I've always usedosascript -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 suggestingkill
or any of its variants.
– TJ Luoma
Mar 30 at 2:58
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
6
This is the best method, because it replicates what happens when you useFile>Quit
from the menu.
– Barmar
Mar 28 at 16:15
2
Huh. I've always usedosascript -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 suggestingkill
or any of its variants.
– TJ Luoma
Mar 30 at 2:58
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
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
MatteoMatteo
5,312135599
5,312135599
6
This is the best method, because it replicates what happens when you useFile>Quit
from the menu.
– Barmar
Mar 28 at 16:15
2
Huh. I've always usedosascript -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 suggestingkill
or any of its variants.
– TJ Luoma
Mar 30 at 2:58
add a comment |
6
This is the best method, because it replicates what happens when you useFile>Quit
from the menu.
– Barmar
Mar 28 at 16:15
2
Huh. I've always usedosascript -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 suggestingkill
or any of its variants.
– TJ Luoma
Mar 30 at 2:58
6
6
This is the best method, because it replicates what happens when you use
File>Quit
from the menu.– Barmar
Mar 28 at 16:15
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
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
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
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.
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 |
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.
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 |
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.
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
user321134user321134
1335
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
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.
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 |
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.
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 |
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.
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
1255
answered Mar 27 at 17:20
BEFioBEFio
811
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.
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 |
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
.
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 ofps
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 usekillall procname
, e.g.killall Slack
and it will kill all occurrences of Slack or whateverprocname
is. No need to useps
!
– user3439894
Mar 29 at 22:26
So,pgrep
is a nice command that combinesps
andgrip
.
– 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
.
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 ofps
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 usekillall procname
, e.g.killall Slack
and it will kill all occurrences of Slack or whateverprocname
is. No need to useps
!
– user3439894
Mar 29 at 22:26
So,pgrep
is a nice command that combinesps
andgrip
.
– 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
.
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
scohe001scohe001
35239
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 ofps
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 usekillall procname
, e.g.killall Slack
and it will kill all occurrences of Slack or whateverprocname
is. No need to useps
!
– user3439894
Mar 29 at 22:26
So,pgrep
is a nice command that combinesps
andgrip
.
– 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 ofps
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 usekillall procname
, e.g.killall Slack
and it will kill all occurrences of Slack or whateverprocname
is. No need to useps
!
– user3439894
Mar 29 at 22:26
So,pgrep
is a nice command that combinesps
andgrip
.
– Harv
Apr 3 at 0:47
2
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
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
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
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
@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
So,
pgrep
is a nice command that combines ps
and grip
.– Harv
Apr 3 at 0:47
add a comment |