11-20-2009
You need to understand that "kill" doesn't create the dump. Kill sends a signal to Jboss ASKING it to dump. You redirected the output of "kill", but it's not "kill" that is going to do the work.
10 More Discussions You Might Find Interesting
1. 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
2. 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
3. UNIX for Advanced & Expert Users
Hellow Experts
i have one problem.
i run one script in backgroun.
and i want to kill that script with only script name.....
so what's the solution..
for your info
my script name is "testscript" n it contains "sleep 100"
thanks.... (16 Replies)
Discussion started by: luckypower
16 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. Shell Programming and Scripting
Hi to everybody.
Is it possible to nohup a process and redirect the output to a file containing the PID?
E.g. if
nohup filename > out.nohup
associate the PID=8074 to filename, is it possible to call the output file something like out_8074.nohup instead of out.nohup? By this way it would... (0 Replies)
Discussion started by: plsrn
0 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
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
8. 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
9. 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
10. Shell Programming and Scripting
Hi All, Looking for a quick LINUX shell script which can continuously monitors the flle size, report the process which is creating a file greater than certain limit and also kill that process. Can someone please help me on this? (4 Replies)
Discussion started by: vasavimacherla
4 Replies
KILL(1) General Commands Manual KILL(1)
NAME
kill - terminate a process with extreme prejudice
SYNOPSIS
kill [ -sig ] processid ...
kill -l
DESCRIPTION
Kill sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first argu-
ment, that signal is sent instead of terminate (see sigvec(2)). The signal names are listed by `kill -l', and are as given in
/usr/include/signal.h, stripped of the common SIG prefix.
The terminate signal will kill processes that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
caught. By convention, if process number 0 is specified, all members in the process group (i.e. processes resulting from the current
login) are signaled (but beware: this works only if you use sh(1); not if you use csh(1).) Negative process numbers also have special
meanings; see kill(2) for details.
The killed processes must belong to the current user unless he is the super-user.
The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using ps(1).
Kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill
arguments. See csh(1) for details.
SEE ALSO
csh(1), ps(1), kill(2), sigvec(2)
BUGS
A replacement for ``kill 0'' for csh(1) users should be provided.
4th Berkeley Distribution April 20, 1986 KILL(1)