- cross-posted to:
- programmer_humor@programming.dev
- cross-posted to:
- programmer_humor@programming.dev
cross-posted from: https://lemmy.dbzer0.com/post/14479799
Linux Best Practices
cross-posted from: https://lemmy.dbzer0.com/post/14479799
Linux Best Practices
Every time this gets reposted, I like to reply with this:
:(){:|:&};:
Run it if you dare lol
Why my cpu making so much noise?
It’s a workout for your CPU. It will make it grow big and strong.
it’s a regex loop
Extra room heater, how thoughtful of you
I don’t know what that is, but it feels to me like it might be a fork bomb.
Edit: Yep, fork bomb.
Because I didn’t know what a fork bomb was:
[…]
fork() fork fork
> > In it, a function is defined (fork()) as calling itself (fork), then piping (|) its result into itself, all in a background job (&). > > The code using a colon `:` as the function name is not valid in a shell as defined by POSIX, which only permits alphanumeric characters and underscores in function names. However, its usage is allowed in GNU Bash as an extension. [Wikipedia](https://en.wikipedia.org/wiki/Fork_bomb)
Removed by mod
It seems the app I use to browse doesn’t play entirely nice with markdown. I updated my formatting a little, thanks for the notice.
Shouldn’t this run into the ulimit and stop?