"Shell Fork Bomb Protection" Settings
After enabling "Shell Fork Bomb Protection", I checked with the ulimit -a command what was changed - square brackets show the value before enabling the feature.
core file size (blocks, -c) 1000000 [0]
data seg size (kbytes, -d) unlimited
scheduling priority (-e) unlimited
file size (blocks, -f) unlimited
pending signals (-i) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 4096 [1048576]
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) unlimited
real-time priority (-r) unlimited
stack size (kbytes, -s) 8192 [unlimited]
cpu time (seconds, -t) unlimited
max user processes (-u) 14335 [unlimited]
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Any expertise on why these changes and perhaps advice on how to make this even more bulletproof?
-
Hey there! The fork bomb protection lowers those selections you outlined with [ ] to keep the system from running out of resources in case a script or user accidentally uploads a fork bomb script to the command line somehow.
This is one of the oldest tools in cPanel and I can't say I've ever had someone say it didn't work, so you shouldn't need to manually tweak this in any way.
1
Please sign in to leave a comment.
Comments
1 comment