From 656373e918c862df92ed1415b4b81da209697325 Mon Sep 17 00:00:00 2001 From: Alexey Avramov Date: Sun, 1 Sep 2019 12:03:18 +0900 Subject: [PATCH] Update readme: fix demo --- README.md | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index 2672554..5f3e05d 100644 --- a/README.md +++ b/README.md @@ -35,18 +35,22 @@ Also look at [Why are low memory conditions handled so badly?](https://www.reddi ## Some features -- Sending the SIGTERM signal is default corrective action. If the victim does not respond to SIGTERM, with a further drop in the level of memory it gets SIGKILL. -- Customizing victim selection: impact on the badness of processes via matching their names, cgroup_v1, cgroup_v2, exe realpathes, environs, cmdlines and euids with specified regular expressions +- Sending the SIGTERM signal is default corrective action. If the victim does not respond to SIGTERM, with a further drop in the level of memory it gets SIGKILL; +- Customizing victim selection: impact on the badness of processes via matching their names, cgroup_v1, cgroup_v2, exe realpathes, environs, cmdlines and euids with specified regular expressions; - Customizing corrective actions: if the name or cgroup_v1 of the victim matches a certain regex pattern, you can run any command instead of sending the SIGTERM signal (the default corrective action) to the victim. For example: - - `sysmemctl restart foo` - - `kill -INT $PID` (you can override the signal sent to the victim, $PID will be replaced by the victim's PID) - - `kill -TERM $PID && script.sh` (in addition to sending any signal, you can run a specified script) + - `sysmemctl restart foo`; + - `kill -INT $PID` (you can override the signal sent to the victim, $PID will be replaced by the victim's PID); + - `kill -TERM $PID && script.sh` (in addition to sending any signal, you can run a specified script). - GUI notifications: - - Notification of corrective actions taken and displaying the name and PID of the victim - - Low memory warnings (displays available memory) -- [zram](https://www.kernel.org/doc/Documentation/blockdev/zram.txt) support (`mem_used_total` as a trigger) -- [PSI](https://lwn.net/Articles/759658/) ([pressure stall information](https://facebookmicrosites.github.io/psi/)) support ([demo](https://youtu.be/2m2c9TGva1Y)) -- Easy configuration with a commented [config file](https://github.com/hakavlad/nohang/blob/master/nohang.conf) + - Notification of corrective actions taken and displaying the name and PID of the victim; + - Low memory warnings (displays available memory). +- [zram](https://www.kernel.org/doc/Documentation/blockdev/zram.txt) support (`mem_used_total` as a trigger); +- [PSI](https://lwn.net/Articles/759658/) ([pressure stall information](https://facebookmicrosites.github.io/psi/)) support; +- Easy configuration with a commented [config file](https://github.com/hakavlad/nohang/blob/master/nohang.conf). + +## Demo + +Nohang v0.1 prevents Out Of Memory with GUI notifications: ([https://youtu.be/ChTNu9m7uMU](https://youtu.be/ChTNu9m7uMU)). ## Requirements