Um es nochmal ein bischen zu praezisieren:
wabbit /wab'it/ /n./ [almost certainly from Elmer Fudd's immortal line "You wascawwy wabbit!"] 1. A legendary early hack reported on a System/360 at RPI and elsewhere around 1978; this may have descended (if only by inspiration) from a hack called RABBITS reported from 1969 on a Burroughs 5500 at the University of Washington Computer Center. The program would make two copies of itself every time it was run, eventually crashing the system. 2. By extension, any hack that includes infinite self-replication
but is not a virus or worm.
rabbit job /n./ [Cambridge] A batch job that does little, if any, real work, but creates one or more copies of itself, breeding like rabbits. Compare wabbit, fork bomb.
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. A fork bomb process `explodes' by recursively spawning copies of itself (using the Unix system call `fork(2)'). Eventually it eats all the process table entries and effectively wedges the system. Fortunately, fork bombs are relatively easy to spot and kill, so creating one deliberately seldom accomplishes more than to bring the just wrath of the gods down upon the perpetrator.
Und weil man jetzt nahezu endlos weiterverweisen koennte verweise ich (mal wieder) auf das Jargonfile.