A zombie process is one that should have closed, but is still active in the process table. This is usually caused when a parent process that spawned the process has not yet realized that it has completed, or wants to create another process of the same name without using the same process ID.
The Linux kernel doesn't consider itself a process, therefore it has no process id.
zombie processes are inherited by the 'init' process (PID 1)
It isn't. RTLinux is a separate microkernel that runs Linux as a process. The Linux kernel is essentially unmodified.
Zombie : Child Process Exits before Parent process and Parent does not grab status of child process using wait() or waitpid() system call; Child process is in Zombie state. Orphan : Child process whose parent has been killed and inherited by init process.
A zombie process is a process that has finished running, but is still there.
Linux is a monolithic kernel. Some operating systems with a microkernel use Linux as a process for providing drivers, but this is irrelevant to mainstream Linux.
in the graveyard
fork
See related links
With the top command.
A zombie process is a process that completed execution but still in process table. When a process ends, all of the memory and resources associated with it are deallocated so they can be used by other processes. However, the process's entry in the process table remains. The parent can read the child's exit status by executing the wait system call, at which stage the zombie is removed After the zombie is removed, its process ID and entry in the process table can then be reused. However, if a parent fails to call wait, the zombie will be left in the process table. In some situations this may be desirable, for example if the parent creates another child process it ensures that it will not be allocated the same process ID.
Any Linux/Unix process that runs in the background is called a 'daemon' process. The word derives from the Greek meaning "worker".