Related:

• zombie n. [Unix] A process that has died but has not yet relinquished its process table slot (because the parent process hasn't executed a wait(2) for it yet).
  These can be seen in ps(1) listings occasionally. Compare orphan....
• orphan: [UNIX] n. A process whose parent has died; one inherited by `init(1)'.
  Compare {zombie}. -- The AI Hackers Dictionary...
• orphan n. [Unix] A process whose parent has died; one inherited by init(1). Compare zombie.
• fork bomb: [UNIX] n. A particular species of {wabbit} that can be written in one line of C (`main() {for(
  )fork();}') or shell (`$0 & $0 &') on any UNIX system, or occasionally created by an egregious coding bug....
• leep: vi. 1. [techspeak] To relinquish a claim (of a process on a multitasking system) for service
  o indicate to the scheduler that a process may be deactivated until some given event occurs or a specified time delay elapses....
• block: [from process scheduling terminology in OS theory] 1.
  vi. To delay or sit idle while waiting for something....
• livelock: /li:v'lok/ n. A situation in which some critical stage of a task is unable to finish because its clients perpetually create more work for it to do after they have been serviced but before it can clear its queue.
  Differs from {deadlock} in that the process is not blocked or waiting for anything, but has a virtually infinite amount of work to do and can never catch up....
• core dump: n. [common {Iron Age} jargon, preserved by UNIX] 1.
  [techspeak] A copy of the contents of {core}, produced when a process is aborted by certain kinds of internal error....
• fork bomb n. [Unix] A particular species of wabbit that can be written in one line of C (main() {for(
  )fork();}) or shell ($0 & $0 &) on any Unix system, or occasionally created by an egregious coding bug....