3 ms·
I came up with a nastier fork bomb about 20 years ago. This also tries to eat your memory. It at least used to reliably hose any *nix system I tried it on, ev
by btilly 5y ago
I came up with a nastier fork bomb about 20 years ago. This also tries to eat your memory. It at least used to reliably hose any *nix system I tried it on, even ones where people had tried to put various process limits in place.
#!/bin/sh
perl -e 'push @big, 1 while 1' &; $0 &; $0
- stjohnswarts 5y agoI wrote a c program that would slowly eat up memory over the course of about 15 minutes and use it to anger fellow college students progressively as the machine became slowly less and less reactive (rather than all at once with fork bombs and such) of course it would back off after a couple minute and start doing it again. After a couple of hours it would exit waiting for the next reboot. I'm glad I'm a lot more mature these days, and my pranks are less about enraging people in student labs. It's my understanding that most of these machine have programs that constantly sweep and delete such things in modern college labs, so that is a good change. Fortunately I grew weary of it after a week or two and deleted it off the few machines I put it on.