How to give arguments to kill via pipe
kill $(ps -e | grep dmn | awk '{print $1}')
Killing linux process by piping the id
Try the backtick operator for evaluating a sub-command
kill -s SIGINT `pgrep -f "python myscript.py"`
(untested)
How to pass command output as multiple arguments to another command
You can use xargs
:
grep 'pattern' input | xargs -I% cp "%" "%.bac"
Find and kill a process in one line using bash and regex
In bash
, you should be able to do:
kill $(ps aux | grep '[p]ython csp_build.py' | awk '{print $2}')
Details on its workings are as follows:
- The
ps
gives you the list of all the processes. - The
grep
filters that based on your search string,[p]
is a trick to stop you picking up the actualgrep
process itself. - The
awk
just gives you the second field of each line, which is the PID. - The
$(x)
construct means to executex
then take its output and put it on the command line. The output of thatps
pipeline inside that construct above is the list of process IDs so you end up with a command likekill 1234 1122 7654
.
Here's a transcript showing it in action:
pax> sleep 3600 &
[1] 2225
pax> sleep 3600 &
[2] 2226
pax> sleep 3600 &
[3] 2227
pax> sleep 3600 &
[4] 2228
pax> sleep 3600 &
[5] 2229
pax> kill $(ps aux | grep '[s]leep' | awk '{print $2}')
[5]+ Terminated sleep 3600
[1] Terminated sleep 3600
[2] Terminated sleep 3600
[3]- Terminated sleep 3600
[4]+ Terminated sleep 3600
and you can see it terminating all the sleepers.
Explaining the grep '[p]ython csp_build.py'
bit in a bit more detail:
When you do sleep 3600 &
followed by ps -ef | grep sleep
, you tend to get two processes with sleep
in it, the sleep 3600
and the grep sleep
(because they both have sleep
in them, that's not rocket science).
However, ps -ef | grep '[s]leep'
won't create a process with sleep
in it, it instead creates grep '[s]leep'
and here's the tricky bit: the grep
doesn't find it because it's looking for the regular expression "any character from the character class [s]
(which is s
) followed by leep
.
In other words, it's looking for sleep
but the grep process is grep '[s]leep'
which doesn't have sleep
in it.
When I was shown this (by someone here on SO), I immediately started using it because
- it's one less process than adding
| grep -v grep
; and - it's elegant and sneaky, a rare combination :-)
How to kill all processes matching a name?
From man 1 pkill
-f The pattern is normally only matched against the process name.
When -f is set, the full command line is used.
Which means, for example, if we see these lines in ps aux
:
apache 24268 0.0 2.6 388152 27116 ? S Jun13 0:10 /usr/sbin/httpd
apache 24272 0.0 2.6 387944 27104 ? S Jun13 0:09 /usr/sbin/httpd
apache 24319 0.0 2.6 387884 27316 ? S Jun15 0:04 /usr/sbin/httpd
We can kill them all using the pkill -f
option:
pkill -f httpd
How to kill all processes with a given partial name?
Use pkill -f
, which matches the pattern for any part of the command line
pkill -f my_pattern
Just in case it doesn't work, try to use this one as well:
pkill -9 -f my_pattern
How to kill a process with 'kill' combined with 'grep'
You want pkill
:
pkill myscriptname
On some systems there is a similar tool called killall
, but be careful because on Solaris it really does kill everything!
Note that there is also pgrep
which you can use to replace your ps | grep
pipeline:
pgrep myscriptname
It prints the PID for you, and nothing else.
kill process with python
You can retrieve the process id (PID) given it name using pgrep
command like this:
import subprocess
import signal
import os
from datetime import datetime as dt
process_name = sys.argv[1]
log_file_name = sys.argv[2]
proc = subprocess.Popen(["pgrep", process_name], stdout=subprocess.PIPE)
# Kill process.
for pid in proc.stdout:
os.kill(int(pid), signal.SIGTERM)
# Check if the process that we killed is alive.
try:
os.kill(int(pid), 0)
raise Exception("""wasn't able to kill the process
HINT:use signal.SIGKILL or signal.SIGABORT""")
except OSError as ex:
continue
# Save old logging file and create a new one.
os.system("cp {0} '{0}-dup-{1}'".format(log_file_name, dt.now()))
# Empty the logging file.
with open(log_file_name, "w") as f:
pass
# Run the process again.
os.sytsem("<command to run the process>")
# you can use os.exec* if you want to replace this process with the new one which i think is much better in this case.
# the os.system() or os.exec* call will failed if something go wrong like this you can check if the process is runninh again.
Hope this can help
Related Topics
Can't Run Executable Linked with Libc
Which Real-Time Priority Is the Highest Priority in Linux
Walking Page Tables of a Process in Linux
Http Debugging Proxy for Linux and MAC
Socat Terminates After Connection Close
Why Can Back-Quotes and $() for Command Substitution Result in Different Output
Posix Shared Memory and Semaphores Permissions Set Incorrectly by Open Calls
What Is the Explanation of This X86 Hello World Using 32-Bit Int 0X80 Linux System Calls from _Start
Start Jboss 7 as a Service on Linux