Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Reminds me of an old SO question about whether the guy made a fork bomb tattoo with a syntax error.
https://stackoverflow.com/questions... -
@CoffeeAndHate It's impossible to kill. It spawns thousands of processes.
Edit: I misread the comment. It freezes pretty quickly, not leaving enough time to do anything. -
Then I guess you can't do anything if the system is unresponsive.
Regarding the commands, I was referring to kill all at once with one command. Something like described in this answer:
https://stackoverflow.com/a/... -
@CoffeeAndHate I guess you could have the time to do this if you have enough RAM
-
@nik123 I'm not really sure since the processes are disowned
-
@nik123 I wasn't sure, so I tested manually. Nope. The solution suggested by @CoffeeAndHate DOES work, but on a VM with 4GB of RAM, I had about 5 seconds to type it.
Another dev on my team just got a new machine. Before he came in today I made two separate USB installers and ...
:(){ :|: & };:
Who has ran this multiple times without ulimit just to see if you could stop it?
undefined
linux
bash
fork bomb