デイヴ on Nostr: Question to #linux geeks and #devops tinkerers: What is the best way to ensure that, ...
Question to #linux geeks and #devops tinkerers:
What is the best way to ensure that, under no circumstances, does my on-prem Debian server let *any* process run amok gobbling up all the RAM/Swap to a point where lack of RAM or IO bottleneck makes it virtually impossible to SSH into the machine to kill the process… (something that tends to happen a lot when I launch a remote Jupyter Notebook to play with LLMs)
Tried with ulimit, cgroup etc, and nothing really sticks…
#debian
What is the best way to ensure that, under no circumstances, does my on-prem Debian server let *any* process run amok gobbling up all the RAM/Swap to a point where lack of RAM or IO bottleneck makes it virtually impossible to SSH into the machine to kill the process… (something that tends to happen a lot when I launch a remote Jupyter Notebook to play with LLMs)
Tried with ulimit, cgroup etc, and nothing really sticks…
#debian