How to avoid a situation where the system is too out-of-memory to even show or kill processes?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I recently ran into a situation where a system was too out-of-memory to even run pkill
or htop
, or to even create a swap file.
(But somehow I could still SSH into the system, so at least I had a shell.)
I ended up getting lucky by noticing that I could run ps
and kill
if I don't run the login shell, but I'm wondering if I hadn't been lucky, what could I have possibly done to avoid rebooting, assuming I still had the login shell?
Is there e.g. to reserve a specific amount of memory for a particular executable to always be able to run? Or is there a way to kill processes from within Bash that doesn't require a fork?
linux bash out-of-memory system-recovery
add a comment |Â
up vote
0
down vote
favorite
I recently ran into a situation where a system was too out-of-memory to even run pkill
or htop
, or to even create a swap file.
(But somehow I could still SSH into the system, so at least I had a shell.)
I ended up getting lucky by noticing that I could run ps
and kill
if I don't run the login shell, but I'm wondering if I hadn't been lucky, what could I have possibly done to avoid rebooting, assuming I still had the login shell?
Is there e.g. to reserve a specific amount of memory for a particular executable to always be able to run? Or is there a way to kill processes from within Bash that doesn't require a fork?
linux bash out-of-memory system-recovery
look at this: unix.stackexchange.com/questions/44985/â¦
â Arpit Agarwal
Nov 11 '17 at 20:40
Probably this will help you: how to create a user with limited ram usage
â FaxMax
Nov 11 '17 at 20:43
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I recently ran into a situation where a system was too out-of-memory to even run pkill
or htop
, or to even create a swap file.
(But somehow I could still SSH into the system, so at least I had a shell.)
I ended up getting lucky by noticing that I could run ps
and kill
if I don't run the login shell, but I'm wondering if I hadn't been lucky, what could I have possibly done to avoid rebooting, assuming I still had the login shell?
Is there e.g. to reserve a specific amount of memory for a particular executable to always be able to run? Or is there a way to kill processes from within Bash that doesn't require a fork?
linux bash out-of-memory system-recovery
I recently ran into a situation where a system was too out-of-memory to even run pkill
or htop
, or to even create a swap file.
(But somehow I could still SSH into the system, so at least I had a shell.)
I ended up getting lucky by noticing that I could run ps
and kill
if I don't run the login shell, but I'm wondering if I hadn't been lucky, what could I have possibly done to avoid rebooting, assuming I still had the login shell?
Is there e.g. to reserve a specific amount of memory for a particular executable to always be able to run? Or is there a way to kill processes from within Bash that doesn't require a fork?
linux bash out-of-memory system-recovery
asked Nov 11 '17 at 20:02
Mehrdad
1,12831430
1,12831430
look at this: unix.stackexchange.com/questions/44985/â¦
â Arpit Agarwal
Nov 11 '17 at 20:40
Probably this will help you: how to create a user with limited ram usage
â FaxMax
Nov 11 '17 at 20:43
add a comment |Â
look at this: unix.stackexchange.com/questions/44985/â¦
â Arpit Agarwal
Nov 11 '17 at 20:40
Probably this will help you: how to create a user with limited ram usage
â FaxMax
Nov 11 '17 at 20:43
look at this: unix.stackexchange.com/questions/44985/â¦
â Arpit Agarwal
Nov 11 '17 at 20:40
look at this: unix.stackexchange.com/questions/44985/â¦
â Arpit Agarwal
Nov 11 '17 at 20:40
Probably this will help you: how to create a user with limited ram usage
â FaxMax
Nov 11 '17 at 20:43
Probably this will help you: how to create a user with limited ram usage
â FaxMax
Nov 11 '17 at 20:43
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f403943%2fhow-to-avoid-a-situation-where-the-system-is-too-out-of-memory-to-even-show-or-k%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
look at this: unix.stackexchange.com/questions/44985/â¦
â Arpit Agarwal
Nov 11 '17 at 20:40
Probably this will help you: how to create a user with limited ram usage
â FaxMax
Nov 11 '17 at 20:43