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) General Commands Manual KILL(1)
NAME
kill, broke - print commands to kill processes
SYNOPSIS
kill name
broke
DESCRIPTION
Kill prints commands that will cause all processes called name and owned by the current user to be terminated. Use the send command of
81/2(1), or pipe the output of kill into rc(1) to execute the commands.
Kill suggests sending a kill note to the process; the same message delivered to the process's ctl file (see proc(3)) is a surer, if heavy
handed, kill, but is necessary if the offending process is ignoring notes.
Broke prints commands that will cause all processes in the Broken state and owned by the current user to go away. When a process dies
because of an error caught by the system, it may linger in the Broken state to allow examination with a debugger. Executing the commands
printed by broke lets the system reclaim the resources used by the broken processes.
SOURCE
/rc/bin/kill
/rc/bin/broke
SEE ALSO
ps(1), stop(1), proc(3)
KILL(1)