05-11-2006
Here..
In UNIX every parent process is responsible for cleaning up after his child processes. As when process is done, its parent process removes it from the system properly and clean its data structure. Sometimes parent process is getting killed or terminated before his child process ends. In such case child process has to be terminated by INIT process. Unfortunately it not always does it clean or perfect.
Zombie processes aren't the real, because there's is no "process" in the execution queue and only some data structure still persist. If they are few just disregard them, as zombi is a normal phase (undesirable but normal) of process's lifetime. If there are many, the only real way to get rid of them is to reboot the system The command "kill", even with -9 wouldn't help as process had been eliminated already.
Get "UNIX Essentials and UNIX Core" DVD as it explains stuff like that.
Hope it helps.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
what is the kill command? (1 Reply)
Discussion started by: Rush
1 Replies
2. Programming
is it possible to implement the kill command using C? (2 Replies)
Discussion started by: kelogs1347
2 Replies
3. UNIX for Dummies Questions & Answers
Hi All,
What is difference between kill & kill -9 command?
Thanks & regards,
Sonali (4 Replies)
Discussion started by: sonali
4 Replies
4. Shell Programming and Scripting
Sorry, posted the question in other forum. (0 Replies)
Discussion started by: sudhamacs
0 Replies
5. 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
6. Shell Programming and Scripting
Hi Guys,
I like to know if i have a process which triggers 10 different child processes.
How to identify out of the 11 processes running which is the parent process and what are the child process?
And if i kill the parent process will the child process be killed.. if not is there a way to... (2 Replies)
Discussion started by: mac4rfree
2 Replies
7. Solaris
I am running Solaris 9. I have a problem with kill command. I'm sort of teaching myself so this might be a really stupid thing. I logged in as a normal user, lets say ABC, and then did "su" to root. After becoming root, I tried to kill the process started by ABC by saying
kill -9 "pid of ABC"
... (3 Replies)
Discussion started by: the_red_dove
3 Replies
8. Shell Programming and Scripting
Good way to kill the process, if the process having it's child (3 Replies)
Discussion started by: pritish.sas
3 Replies
9. Shell Programming and Scripting
hello, can anyone help me with a script that checks the status of processes and "kills" the process that's hanging? I mean I'm aware of the commands but I'm confused on how to put them all together... thanks! :) (4 Replies)
Discussion started by: dude911
4 Replies
10. UNIX for Dummies Questions & Answers
what is the difference between kill 5 and kill %5? the first one is to kill a process with PID 5 but what does the % mean in the second one? (3 Replies)
Discussion started by: chinababy
3 Replies
KILL(2) Linux Programmer's Manual KILL(2)
NAME
kill - send signal to a process
SYNOPSIS
#include <sys/types.h>
#include <signal.h>
int kill(pid_t pid, int sig);
DESCRIPTION
The kill system call can be used to send any signal to any process group or process.
If pid is positive, then signal sig is sent to pid.
If pid equals 0, then sig is sent to every process in the process group of the current process.
If pid equals -1, then sig is sent to every process except for process 1 (init), but see below.
If pid is less than -1, then sig is sent to every process in the process group -pid.
If sig is 0, then no signal is sent, but error checking is still performed.
RETURN VALUE
On success, zero is returned. On error, -1 is returned, and errno is set appropriately.
ERRORS
EINVAL An invalid signal was specified.
ESRCH The pid or process group does not exist. Note that an existing process might be a zombie, a process which already committed termi-
nation, but has not yet been wait()ed for.
EPERM The process does not have permission to send the signal to any of the receiving processes. For a process to have permission to send
a signal to process pid it must either have root privileges, or the real or effective user ID of the sending process must equal the
real or saved set-user-ID of the receiving process. In the case of SIGCONT it suffices when the sending and receiving processes
belong to the same session.
NOTES
It is impossible to send a signal to task number one, the init process, for which it has not installed a signal handler. This is done to
assure the system is not brought down accidentally.
POSIX 1003.1-2001 requires that kill(-1,sig) send sig to all processes that the current process may send signals to, except possibly for
some implementation-defined system processes. Linux allows a process to signal itself, but on Linux the call kill(-1,sig) does not signal
the current process.
LINUX HISTORY
Across different kernel versions, Linux has enforced different rules for the permissions required for an unprivileged process to send a
signal to another process. In kernels 1.0 to 1.2.2, a signal could be sent if the effective user ID of the sender matched that of the
receiver, or the real user ID of the sender matched that of the receiver. From kernel 1.2.3 until 1.3.77, a signal could be sent if the
effective user ID of the sender matched either the real or effective user ID of the receiver. The current rules, which conform to POSIX
1003.1-2001, were adopted in kernel 1.3.78.
CONFORMING TO
SVr4, SVID, POSIX.1, X/OPEN, BSD 4.3, POSIX 1003.1-2001
SEE ALSO
_exit(2), exit(3), signal(2), signal(7)
Linux 2.5.0 2001-12-18 KILL(2)