Since I'm newbie in Linux/Unix systems and just read about zombie processes, I have one question. I have 10 of them right now. Do I need to kill them and if yes, why? Are they a load on my system?
592 processes: 581 sleeping, 1 running, 10 zombie, 0 stopped
You cannot kill a zombie, it is already dead.
The resources of that process are free and available to other processes. What remains is an entry in the process table. This does not have an influence on the performance, don't worry.
What are these zombie processes that show up in ps? I kill them but they don't go away!
Zombies are dead processes. You cannot kill the dead. All processes eventually die, and when they do they become zombies. They consume almost no resources, which is to be expected because they are dead! The reason for zombies is so the zombie's parent (process) can retrieve the zombie's exit status and resource usage statistics. The parent signals the operating system that it no longer needs the zombie by using one of the wait() system calls.
When a process dies, its child processes all become children of process number 1, which is the init process. Init is always waiting for children to die, so that they don't remain as zombies.
If you have zombie processes it means those zombies have not been waited for by their parent (look at PPID displayed by ps -l). You have three choices: Fix the parent process (make it wait); kill the parent; or live with it. Remember that living with it is not so hard because zombies take up little more than one extra line in the output of ps.
Source: http://www.linuxsa.org.au/tips/zombies.html
And in case you’re on a killing spree, this superuser thread might be interesting to you: How do you find the parent process of a zombie process?
You don't need to kill them.
To build up some basic understanding:
Every process is the child of a parent process (except for the init process, but we don't need to worry about that).
When a child process finishes executing, it might still contain data that the parent process wants to access, usually an exit code which describes the result of the child process (Did it succeed? Did it error? What was the error code?).
A finished child process hangs around in the process table as a zombie process until the parent process "reaps" or waits on the child process, which is simply the parent process telling the OS that it doesn't need that child process anymore; It has read any return values it wants, and is done with it. At this point, the system will clean up the entry in the process table.
This process doesn't need to be killed.
Just in case you do want to kill it anyway (for whatever reason), make sure you shoot at the head, here is a useful command:
kill -HUP `ps -A -ostat,ppid | grep -e '^[Zz]' | awk '{print $2}'`
