08-02-2008
Something simple:
killall procname
Another way:
inside your script, create a temporary file that holds the current pid of your script. When you wish to terminate the process, use that as such: kill -9 `cat pidfile`
If you want something very specific and accurate:
- setuid() to another user which only runs that process (script)
- pkill -9 -u youruser
You can also use pkill to kill all processes using a certain terminal pkill -9 -t pts/1
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi, i kill a process which is topas. then i do a fg of the process itself and got this Signal 15 received.finally, the display went as belows....
root@myhost:/]ksh: ^L^L^Lps: not found.
root@myhost:/] PID TTY TIME CMD
... (4 Replies)
Discussion started by: yls177
4 Replies
2. Shell Programming and Scripting
Hi there, i wonder if anyone can help
is there any way that i can write a script that will kill all current ftp processes, for example if ps -ef | grep ftp produces 3 active proceses, then I would like to somehow extract the PID for each one and pass that to kill -9
has anybody done this... (2 Replies)
Discussion started by: hcclnoodles
2 Replies
3. Shell Programming and Scripting
Hi All,
In my project i have two process runs in the back end.
Once i start my project, and execute the command ps, i get below output:
PID TTY TIME CMD
9086 pts/1 0:00 ksh
9241 pts/1 0:02 java
9240 pts/1 0:00 shell_script_bg
java with 9241 PID is the main... (4 Replies)
Discussion started by: rkrgarlapati
4 Replies
4. Shell Programming and Scripting
Hi,
On my Linux machine, using Bash, I sometimes run into a situation where doing the following does not seem to work at all.
kermit@fastbox ~ $ ps -A | grep firefox-bin
5375 ? 00:06:57 firefox-bin <defunct>
5624 ? 00:00:00 firefox-bin
kermit@fastbox ~ $ kill 5624... (7 Replies)
Discussion started by: kermit
7 Replies
5. AIX
Hi all,
I am generating the coredump of my JBoss, and by default it puts it in to a particular directory. i.e. JBOSS_HOME/. I would like this output file to be created, lets say in /tmp/dump/.
I tried the following:
kill -3 9404940>/tmp/dump/out.txt
But it created... (3 Replies)
Discussion started by: haroon_a
3 Replies
6. UNIX for Dummies Questions & Answers
Hello,
I have problem with killing red5 process running on linux server. As this process is continuously changing its PID so it can't be killed with "kill -9 PID" command.
First I used following command to list RED5 process
ps aux | grep red5
which showed me
root 5832 0.0 0.0 4820 756pts/0... (1 Reply)
Discussion started by: ninadgac
1 Replies
7. Shell Programming and Scripting
Hello,
I have problem with killing red5 process running on linux server. As this process is continuously changing its PID so it can't be killed with "kill -9 PID" command.
First I used following command to list RED5 process
ps aux | grep red5
which showed me
root 5832 0.0 0.0 4820 756pts/0... (4 Replies)
Discussion started by: ninadgac
4 Replies
8. Shell Programming and Scripting
Hi,
I wrote a script to kill a process id.
I am able to kill the PID only if I enter the root password in the middle of the execution because I did not run as root i.e after i run the script from the terminal, instead of killing directly, it is killing only after entering the pass when it... (12 Replies)
Discussion started by: rajkumarme_1
12 Replies
9. Shell Programming and Scripting
Hello Friends,
I've been trying to write a one line which checks java processes and filter them for a user (testuser) and then check process arguments with PARGS command and then check if there is certain patterns exists in pargs output then kill the process.
I have tried the following so... (2 Replies)
Discussion started by: EAGL€
2 Replies
10. AIX
I created a program to kill long running pid processes.
I am getting the following error message:
-f command cannot be found.
I also want to count the number of pids that are killed and append the results to a text file. I am new to shell script programming.
1.The first part of code... (10 Replies)
Discussion started by: dellanicholson
10 Replies
PKILL(1) BSD General Commands Manual PKILL(1)
NAME
pgrep, pkill -- find or signal processes by name
SYNOPSIS
pgrep [-Lafilnoqvx] [-F pidfile] [-G gid] [-P ppid] [-U uid] [-d delim] [-g pgrp] [-t tty] [-u euid] pattern ...
pkill [-signal] [-ILafilnovx] [-F pidfile] [-G gid] [-P ppid] [-U uid] [-g pgrp] [-t tty] [-u euid] pattern ...
DESCRIPTION
The pgrep command searches the process table on the running system and prints the process IDs of all processes that match the criteria given
on the command line.
The pkill command searches the process table on the running system and signals all processes that match the criteria given on the command
line.
The following options are available:
-F pidfile Restrict matches to a process whose PID is stored in the pidfile file.
-G gid Restrict matches to processes with a real group ID in the comma-separated list gid.
-I Request confirmation before attempting to signal each process.
-L The pidfile file given for the -F option must be locked with the flock(2) syscall or created with pidfile(3).
-P ppid Restrict matches to processes with a parent process ID in the comma-separated list ppid.
-U uid Restrict matches to processes with a real user ID in the comma-separated list uid.
-d delim Specify a delimiter to be printed between each process ID. The default is a newline. This option can only be used with the
pgrep command.
-a Include process ancestors in the match list. By default, the current pgrep or pkill process and all of its ancestors are
excluded (unless -v is used).
-f Match against full argument lists. The default is to match against process names.
-g pgrp Restrict matches to processes with a process group ID in the comma-separated list pgrp. The value zero is taken to mean the
process group ID of the running pgrep or pkill command.
-i Ignore case distinctions in both the process table and the supplied pattern.
-l Long output. For pgrep, print the process name in addition to the process ID for each matching process. If used in conjunction
with -f, print the process ID and the full argument list for each matching process. For pkill, display the kill command used for
each process killed.
-n Select only the newest (most recently started) of the matching processes.
-o Select only the oldest (least recently started) of the matching processes.
-q Do not write anything to standard output.
-t tty Restrict matches to processes associated with a terminal in the comma-separated list tty. Terminal names may be of the form
ttyxx or the shortened form xx. A single dash ('-') matches processes not associated with a terminal.
-u euid Restrict matches to processes with an effective user ID in the comma-separated list euid.
-v Reverse the sense of the matching; display processes that do not match the given criteria.
-x Require an exact match of the process name, or argument list if -f is given. The default is to match any substring.
-signal A non-negative decimal number or symbolic signal name specifying the signal to be sent instead of the default TERM. This option
is valid only when given as the first argument to pkill.
If any pattern operands are specified, they are used as regular expressions to match the command name or full argument list of each process.
Note that a running pgrep or pkill process will never consider itself as a potential match.
EXIT STATUS
The pgrep and pkill utilities return one of the following values upon exit:
0 One or more processes were matched.
1 No processes were matched.
2 Invalid options were specified on the command line.
3 An internal error occurred.
SEE ALSO
kill(1), killall(1), ps(1), flock(2), kill(2), sigaction(2), pidfile(3), re_format(7)
HISTORY
The pkill and pgrep utilities first appeared in NetBSD 1.6. They are modelled after utilities of the same name that appeared in Sun Solaris
7. They made their first appearance in FreeBSD 5.3.
AUTHORS
Andrew Doran <ad@NetBSD.org>
BSD
February 11, 2010 BSD