github/nohang
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix logging: add logrotate

Browse Source
This commit is contained in:
Alexey Avramov 2019-03-20 21:59:19 +09:00
parent 7d13107463
commit 44d7459fa6
1 changed files with 12 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -51,7 +51,7 @@ The tools listed above may work at the same time on one computer.
- Notification of corrective actions taken and displaying the name and PID of the victim - Notification of corrective actions taken and displaying the name and PID of the victim
- Low memory warnings (displays available memory) - Low memory warnings (displays available memory)
- `zram` support (`mem_used_total` as a trigger) - `zram` support (`mem_used_total` as a trigger)
- Initial [PSI](https://lwn.net/Articles/759658/) ([pressure stall information](https://facebookmicrosites.github.io/psi/)) support - Initial [PSI](https://lwn.net/Articles/759658/) ([pressure stall information](https://facebookmicrosites.github.io/psi/)) support ([demo](https://youtu.be/2m2c9TGva1Y))
- Easy configuration with a ~~well~~ commented [config file](https://github.com/hakavlad/nohang/blob/master/nohang.conf) - Easy configuration with a ~~well~~ commented [config file](https://github.com/hakavlad/nohang/blob/master/nohang.conf)
## Requirements ## Requirements
@ -131,14 +131,16 @@ optional arguments:
The program can be configured by editing the [config file](https://github.com/hakavlad/nohang/blob/master/nohang.conf). The configuration includes the following sections: The program can be configured by editing the [config file](https://github.com/hakavlad/nohang/blob/master/nohang.conf). The configuration includes the following sections:
1. Memory levels to respond to as an OOM threat 1. Memory levels to respond to as an OOM threat
2. The frequency of checking the level of available memory (and CPU usage) 2. Response on PSI memory metrics
3. The prevention of killing innocent victims 3. The frequency of checking the level of available memory (and CPU usage)
4. Impact on the badness of processes via matching their names, cmdlines and UIDs with regular expressions 4. The prevention of killing innocent victims
5. The execution of a specific command or sending any signal instead of sending the SIGTERM signal 5. Impact on the badness of processes via matching their names, cmdlines and UIDs with regular expressions
6. GUI notifications: 6. The execution of a specific command or sending any signal instead of sending the SIGTERM signal
7. GUI notifications:
- notifications of corrective actions taken - notifications of corrective actions taken
- low memory warnings - low memory warnings
7. Output verbosity 8. Verbosity
9. Misc
Just read the description of the parameters and edit the values. Please restart nohang to apply changes. Default path to the config after installing is `/etc/nohang/nohang.conf`. Just read the description of the parameters and edit the values. Please restart nohang to apply changes. Default path to the config after installing is `/etc/nohang/nohang.conf`.
@ -184,6 +186,8 @@ $ sudo journalctl -eu nohang
``` ```
See also `man journalctl`. See also `man journalctl`.
On non-systemd systems you can enable `separate_log` in config to logging in `/var/log/nohang/nohang.log`.
## Known problems ## Known problems
- Awful documentation. - Awful documentation.