Comment Re:cat food (Score 4, Informative) 26
"That command is a classic example of a fork bomb.
What it does
When executed in a POSIX-compliant shell (like Bash), this command causes the system to rapidly consume all available resources by creating an exponential number of processes until the system crashes or becomes completely unresponsive.
Breakdown of the syntax
Here is how that cryptic string is interpreted by the shell:
:(): This defines a function named :.
{ ... }: This defines the body of the function.
:|:: This calls the function : and pipes its output to another instance of the function :.
&: This puts the function call into the background, so the parent process doesn't wait for it to finish.
;: This terminates the function definition.
:: This final character executes the function for the first time, triggering the cycle.
Essentially, the function calls itself twice, and because it runs in the background, each call continues to spawn more copies of itself uncontrollably.
Important Warning
Do not run this command on your computer.
If you execute this, your system will likely become unresponsive, requiring a hard reboot to clear the process table and recover. On many modern Linux distributions, there are default security limits (ulimit) in place that prevent a single user from spawning enough processes to crash the entire system, but it is still highly inadvisable to test it."
What it does
When executed in a POSIX-compliant shell (like Bash), this command causes the system to rapidly consume all available resources by creating an exponential number of processes until the system crashes or becomes completely unresponsive.
Breakdown of the syntax
Here is how that cryptic string is interpreted by the shell:
{
&: This puts the function call into the background, so the parent process doesn't wait for it to finish.
Essentially, the function calls itself twice, and because it runs in the background, each call continues to spawn more copies of itself uncontrollably.
Important Warning
Do not run this command on your computer.
If you execute this, your system will likely become unresponsive, requiring a hard reboot to clear the process table and recover. On many modern Linux distributions, there are default security limits (ulimit) in place that prevent a single user from spawning enough processes to crash the entire system, but it is still highly inadvisable to test it."