05-11-2006
If it has died and is now a zombie, killing the parent process will cause it to be re-parented to init which will reap it. But if it is sleeping at a high kernel priority, the only general answer is to reboot the system. Since you're on HP-UX, you should use glance to examine the process and determine what it is waiting for. Then there is some chance that you can correct it. For example, if it is trying to close a tape drive that has been powered off, bringing the tape drive back online may allow the close to succeed. Or maybe it is trying to write to /dev/console and someone typed an X-off (control s), so typing an X-on (control q) may allow the write to finish. If it is doing disk i/o to an NFS mounted filesystem with nointr, fixing the NFS server or the network may do it. Or maybe it is a bug in the kernel and so you want to identify what resource it is waiting for and then check for patches that look applicable. This won't help kill the particular process you have now, but patching the kernel would insure it doesn't keep on happening.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
how to start a process and make it sleep for 5 mins and then kill that process (6 Replies)
Discussion started by: shrao
6 Replies
2. Programming
Hi all
i have simple c program , when i wish to kill the app
im using kill(0,-9) , but it seams this command don't do any thing and the program.
just ignore it .
what im doing wrong here ?
im using HP-UX ia64
Thanks (9 Replies)
Discussion started by: umen
9 Replies
3. Solaris
Hi,
how can i kill one running process, how can i get the process id
thanks .BJ (5 Replies)
Discussion started by: bennichan
5 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
Sorry, posted the question in other forum. (0 Replies)
Discussion started by: sudhamacs
0 Replies
6. Linux
I want to Kill a process without using kill command as i don't have privileges to kill the process. I know the pid and i am using Linux 2.6.9 OS. (6 Replies)
Discussion started by: sudhamacs
6 Replies
7. Shell Programming and Scripting
Hi Experts, we do have a shell script for Unix Solaris, which will kill all the process manullay, it used to work in my previous env, but now it is throwing this error.. could some one please help me to resolve it
This is how we execute the script (and this is the requirement) ... (2 Replies)
Discussion started by: jonnyvic
2 Replies
8. UNIX for Dummies Questions & Answers
What I need to learn is how to use a script that launches background processes, and then kills those processes as needed.
The script successfully launches the script. But how do I check to see if the job exists before I kill it?
I know my problem is mostly failure to understand parameter... (4 Replies)
Discussion started by: holocene
4 Replies
9. Solaris
Hello everyone,
I have a process that I want to kill. I have tried kill-9 PID but it doesn't work. I have tried preap PID but it doesn't work too.
The parent of my process is the process whose PID is 1, so I can't kill it.
My OS is a Solaris 9.
Can anyone help me understand what's going... (3 Replies)
Discussion started by: adilyos
3 Replies
10. Shell Programming and Scripting
Good afternoon
I need to KILL a process in a single command sentence, for example:
kill -9 `ps -aef | grep 'CAL255.4ge' | grep -v grep | awk '{print $2}'`
That sentence Kills the process ID corresponding to the program CAL255.4ge.
However it is possible that the same program... (6 Replies)
Discussion started by: enriquegm82
6 Replies
KILL(1) BSD General Commands Manual KILL(1)
NAME
kill -- terminate or signal a process
SYNOPSIS
kill [-s signal_name] pid ...
kill -l [exit_status]
kill -signal_name pid ...
kill -signal_number pid ...
DESCRIPTION
The kill utility sends a signal to the processes specified by the pid operands.
Only the super-user may send signals to other users' processes.
The options are as follows:
-s signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-l [exit_status]
If no operand is given, list the signal names; otherwise, write the signal name corresponding to exit_status.
-signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-signal_number
A non-negative decimal integer, specifying the signal to be sent instead of the default TERM.
The following PIDs have special meanings:
-1 If superuser, broadcast the signal to all processes; otherwise broadcast to all processes belonging to the user.
Some of the more commonly used signals:
1 HUP (hang up)
2 INT (interrupt)
3 QUIT (quit)
6 ABRT (abort)
9 KILL (non-catchable, non-ignorable kill)
14 ALRM (alarm clock)
15 TERM (software termination signal)
Some shells may provide a builtin kill command which is similar or identical to this utility. Consult the builtin(1) manual page.
EXIT STATUS
The kill utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
Terminate the processes with PIDs 142 and 157:
kill 142 157
Send the hangup signal (SIGHUP) to the process with PID 507:
kill -s HUP 507
SEE ALSO
builtin(1), csh(1), killall(1), ps(1), sh(1), kill(2), sigaction(2)
STANDARDS
The kill utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
HISTORY
A kill command appeared in Version 3 AT&T UNIX.
BUGS
A replacement for the command ``kill 0'' for csh(1) users should be provided.
BSD
April 28, 1995 BSD