Bash , 12##12
Note: This is destructive.
:(){ :|:&};:
It's the popular bash fork-bomb. It exponentially eats all memory and PID's locking up the system. A hard-reboot will allow the code to be run again though why would you want to do that?
Bash , 10
:(){ :&};:
For two less chars, this eats your memory linearly.
Bash , 7
w;PATH=
w is chosen as the shortest executable that I could think of.
This simply erases the path variable so the shell can't find /usr/bin/w the next time. Restarting the shell fixes it as the path is usually stored in ~/.profile
Bash , 12##
Note: This is destructive.
:(){ :|:&};:
It's the popular bash fork-bomb. It exponentially eats all memory and PID's locking up the system. A hard-reboot will allow the code to be run again though why would you want to do that?
Bash , 10
:(){ :&};:
For two less chars, this eats your memory linearly.
Bash , 7
w;PATH=
w is chosen as the shortest executable that I could think of.
This simply erases the path variable so the shell can't find /usr/bin/w the next time. Restarting the shell fixes it as the path is usually stored in ~/.profile
Bash , 12
Note: This is destructive.
:(){ :|:&};:
It's the popular bash fork-bomb. It exponentially eats all memory and PID's locking up the system. A hard-reboot will allow the code to be run again though why would you want to do that?
Bash , 10
:(){ :&};:
For two less chars, this eats your memory linearly.
Bash , 7
w;PATH=
w is chosen as the shortest executable that I could think of.
This simply erases the path variable so the shell can't find /usr/bin/w the next time. Restarting the shell fixes it as the path is usually stored in ~/.profile
Bash , 12##
Note: This is destructive.
:(){ :|:&};:
It's the popular bash fork-bomb. It exponentially eats all memory and PID's locking up the system. A hard-reboot will allow the code to be run again though why would you want to do that?
Bash , 10
:(){ :&};:
For two less chars, this eats your memory linearly.
Bash , 7
w;PATH=
w is chosen as the shortest executable that I could think of.
This simply erases the path variable so the shell can't find /usr/bin/w the next time. Restarting the shell fixes it as the path is usually stored in ~/.profile
Bash , 12##
Note: This is destructive.
:(){ :|:&};:
It's the popular bash fork-bomb. It exponentially eats all memory and PID's locking up the system. A hard-reboot will allow the code to be run again though why would you want to do that?
Bash , 10
:(){ :&};:
For two less chars, this eats your memory linearly.
Bash , 12##
Note: This is destructive.
:(){ :|:&};:
It's the popular bash fork-bomb. It exponentially eats all memory and PID's locking up the system. A hard-reboot will allow the code to be run again though why would you want to do that?
Bash , 10
:(){ :&};:
For two less chars, this eats your memory linearly.
Bash , 7
w;PATH=
w is chosen as the shortest executable that I could think of.
This simply erases the path variable so the shell can't find /usr/bin/w the next time. Restarting the shell fixes it as the path is usually stored in ~/.profile
Bash , 12##
Note: This is destructive.
:(){ :|:&};:
It's the popular bash fork-bomb. It exponentially eats all memory and PID's locking up the system. A hard-reboot will allow the code to be run again though why would you want to do that?
Bash , 10
:(){ :&};:
For two less chars, this eats your memory linearly.