A zombie is a mythical creature, a dead human that's somehow woken up and moves about again. An orphan is a child that has lost both parents.
zombie processes are inherited by the 'init' process (PID 1)
A zombie process is basically a process that stops responding, to put it in simple terms.
A zombie process is a process that has finished running, but is still there.
in the graveyard
Usually any orphaned process is owned by the 'init' process (process #1)
If processes run on nodes that have derailed so to speak or the tm.watched yk has been activated, the process is considered orphaned. The watch deamons are set to kill the orphan process on default.
See related links
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.
A zombification is the act or process of turning into a zombie.
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.