How To Kill The Largest Process In An Unresponsive Linux System

Early OOM - Kill The Largest Process

4 Responses

  1. Aditya Goturu says:

    Its going to kill Apache isn’t it?

  2. IJK says:

    Far less useful than one might think – in a scarce memory situation, you might not even be able to issue any commands, much less spawning a shell to do so.

    • Mike says:

      Isn’t the point that it kills the largest processes automatically? Usually, when a system freezes, we realize what is happening and we want to kill some programs manually but we can’t. This will do that and then we can, for example, restore browser session afterward if the browser will be killed, despite what it says in the article.

  3. Bobo says:

    See like a interesting solution for unresponsive system. My only concern is if there is maybe something like time option – if system is more then 5 minutes with very high memory usage then kill that procces. But it’s a nice thing to have definitly!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.