デイヴ 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
Published at
2025-01-14 06:01:03Event JSON
{
"id": "b60679d8b24c2d5ecfa73ef77f7ce4a4f57b270c7539e621ed50da401d7d05c3",
"pubkey": "8a3fd5c5bc8b8baa323eb57dc2970ec492fdb3b8f79b12dfff8c9c921a18833e",
"created_at": 1736834463,
"kind": 1,
"tags": [
[
"t",
"debian"
],
[
"t",
"linux"
],
[
"t",
"devops"
],
[
"proxy",
"https://mastodon.social/users/deivudesu/statuses/113825183387765967",
"activitypub"
]
],
"content": "Question to #linux geeks and #devops tinkerers:\n\nWhat 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)\n\nTried with ulimit, cgroup etc, and nothing really sticks…\n\n#debian",
"sig": "0a4b5b77d5fe336b9829bb4829ea049051a2dd7b45108aa1ec94267556cace66c0bdfce14354609867b91f15d120167266d8a3873b3f144e954cabdcc2b7049e"
}