From 5ca9f249b15d7567efe6eefd928cd45b37869d30 Mon Sep 17 00:00:00 2001 From: Alexey Avramov Date: Wed, 25 Jul 2018 04:27:29 +0900 Subject: [PATCH] update readme --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ac7efdd..bd327c6 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@ Nohang is a highly configurable daemon for Linux which is able to correctly prev ## What is the problem? -OOM conditions may cause [freezes](https://en.wikipedia.org/wiki/Hang_(computing)), [livelocks](https://en.wikipedia.org/wiki/Deadlock#Livelock), drop [caches](https://en.wikipedia.org/wiki/Page_cache) and processes to be killed (via [SIGKILL](https://en.wikipedia.org/wiki/Signal_(IPC)#SIGKILL)) instead of trying to terminate them correctly (via [SIGTERM](https://en.wikipedia.org/wiki/Signal_(IPC)#SIGTERM) or other action). Some applications may crash if it's impossible to allocate memory. +OOM conditions may cause [freezes](https://en.wikipedia.org/wiki/Hang_(computing)), [livelocks](https://en.wikipedia.org/wiki/Deadlock#Livelock), drop [caches](https://en.wikipedia.org/wiki/Page_cache) and processes to be killed (via sending [SIGKILL](https://en.wikipedia.org/wiki/Signal_(IPC)#SIGKILL)) instead of trying to terminate them correctly (via sending [SIGTERM](https://en.wikipedia.org/wiki/Signal_(IPC)#SIGTERM) or takes other corrective action). Some applications may crash if it's impossible to allocate memory. Here are the statements of some users: