Running a fork-bomb on Linux :(){ :|: & };: - You Suck at Programming #016

VM cringe. Production server based.

Okay. How do you limit this? Surely there’s some kind of security feature that limits max amount of processes/ram/resources a user is allowed to create and use.

but... NCIS told me this would catch the system on fire :(

1. Ulimit exists. All sane systems limit the number of processes.
2. Learn Magic SysRq keys. They talk directly to the kernel and work regardless of how clogged the system is, saving you from pulling the plug in most scenarios.

Hey, when I first saw the thumbnail, I thought you were RMS's evil twin. Watching the first few seconds of the video just confirmed my hunch

try it on fish shell 😉

also void is cringe it deserves the fork bomb

It would really suck if someone made a service with a fork bomb, enabled it, and it starts up every time you boot up Void Linux.

In college when we submitted assignments, the instructor had it set up to automatically compile and run your code.

People realized they could put a fork bomb in their code and crash the project submission server.

The instructor asked us very nicely to not be malicious, and that logs are being kept.

We had fun, the professor was cool, and the fork bombs stopped.