645

Rule for Beginners (lemmy.world)

submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]

61 comments fedilink hide all child comments

cross-posted from: https://lemmy.dbzer0.com/post/14479799

Linux Best Practices

you are viewing a single comment's thread
view the rest of the comments

[-] [email protected] 67 points 7 months ago

Every time this gets reposted, I like to reply with this:

:(){:|:&};:

Run it if you dare lol

[-] [email protected] 40 points 7 months ago

Why my cpu making so much noise?

[-] [email protected] 37 points 7 months ago

It's a workout for your CPU. It will make it grow big and strong.

[-] [email protected] 2 points 7 months ago

it's a regex loop

[-] [email protected] 32 points 7 months ago

Extra room heater, how thoughtful of you

[-] [email protected] 2 points 7 months ago* (last edited 7 months ago)

I don't know what that is, but it feels to me like it might be a fork bomb.

Edit: Yep, fork bomb.

[-] [email protected] 3 points 7 months ago* (last edited 7 months ago)

Because I didn't know what a fork bomb was:

a fork bomb is a denial-of-service (DoS) attack wherein a process continually replicates itself to deplete available system resources, slowing down or crashing the system due to resource starvation.

[...]

A classic example of a fork bomb is one written in Unix shell :(){ :|:& };:, possibly dating back to 1999, which can be more easily understood as

fork() { 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 (&amp;).
> 
> 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)

[-] [email protected] 1 points 7 months ago* (last edited 7 months ago)

You're telling markdown to format the code in the language fork() { and then break the code block early by not having > in front of the next line. Here's a quoted code block formatted in sh:

fork() {
   fork | fork &
}
fork

[-] [email protected] 1 points 7 months ago

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.

[-] [email protected] 1 points 7 months ago* (last edited 7 months ago)

Shouldn't this run into the ulimit and stop?

this post was submitted on 16 Feb 2024

645 points (100.0% liked)

196

16240 readers

1753 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 1 year ago

MODERATORS

[email protected]