Tested it on my macbook which is bsd based, and surprisingly there was a level of protection, so it didn't crash my system interestingly enough! Great video!
I don't get why there's a pipilne there. Like I always thought that command1 | command2 redirects the output of the command1 to the input of the command2 Why is it :|: and not something like :&&: ???
Great question, and you're correct about the pipe. In this case, the actual data or output being passed through the pipe is not used. If a process takes nothing into stdin, you can still pipe to it. Using && would make the second call dependent on the successful completion of the first call, and so the pipe is used to execute both recursive calls in parallel without conditions. To your point, ":(){ :&:; }; :" will also work in most cases.
Making that function more readable is an awesome way of teaching what it does.
So basically a nuclear bomb
Greta video, honestly. Well-spoken, confident, nice editing. Wish you look at growing big
Tested it on my macbook which is bsd based, and surprisingly there was a level of protection, so it didn't crash my system interestingly enough! Great video!
iirc most distros using systemd mitigate forkbombs by setting a ulimit
Yep, you can set limits on systemd unit files, and you can also set a ulimit to a smaller value in login scripts.
This was pretty cool.
why no comments man
This was nice.😅
I don't get why there's a pipilne there. Like I always thought that command1 | command2 redirects the output of the command1 to the input of the command2
Why is it :|: and not something like :&&: ???
Great question, and you're correct about the pipe. In this case, the actual data or output being passed through the pipe is not used. If a process takes nothing into stdin, you can still pipe to it. Using && would make the second call dependent on the successful completion of the first call, and so the pipe is used to execute both recursive calls in parallel without conditions. To your point, ":(){ :&:; }; :" will also work in most cases.
@@MalwareCube thx for making this clear
Why make it so unnecessarily complex? Just keep it simple and run "make -j"
one liner admin is better
?