3 ms·
How is that not a fork bomb? ("The author disagrees with this characterization, which was added by an editor late in the publication process.")
by CamperBob2 8y ago
How is that not a fork bomb? ("The author disagrees with this characterization, which was added by an editor late in the publication process.")
- nneonneo 8y agoThe parent always exits (fork() returns the nonzero child pid in the parent, and 0 in the child), meaning that at any point there’s only one process that is actively forking. A typical fork bomb, on the other hand, floods the system with processes that are all attempting to call fork, resulting in an exponentially growing set of processes until the system runs out of resources.
- CGamesPlay 8y agoBecause the number of live processes never exceeds 2, and fork bombs typically refer to DoS attacks by exhausting the PID space.
- deleted 8y ago[deleted]
- userbinator 8y agoI propose the term "forkworm", or perhaps "forxolotl"[1] for these processes that continuously reproduce but don't grow exponentially. [1] https://en.wikipedia.org/wiki/Axolotl#Regeneration https://en.wikipedia.org/wiki/Axolotl#Regeneration
- caf 8y agoIt already has a name - processes like this were historically called "comets".
- OskarS 8y agoThis is a fork bomb: while (1) { fork(); } This will fork forever, creating children that fork forever, exhausting the system's resources. The example in the article only ever has at most 2 processes, and they don't exhaust anything.
- glandium 8y agoNote yours is an exponential fork bomb: both parent and child processes keep forking.