From 26f496dee90306cddf2a19370f44ed60e2d70cb6 Mon Sep 17 00:00:00 2001 From: Edo Date: Fri, 21 Jul 2023 18:15:59 +0200 Subject: [PATCH] maint: update README --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 4596741..8ca2cc0 100644 --- a/README.md +++ b/README.md @@ -1,10 +1,10 @@ # MonitorRam -A simple program that monitors real memory usage of processes. +A simple program that monitors the real memory usage of processes. # Example I have multiple processes, and all of them are named similarly. In my case, all the processes I need to monitor begin with the same string. The program will monitor up to 30 different processes; the max value is defined in `monitor.c`. -I would start this program using the following command: `./monitor iw5`. It will monitor all my game servers as they all share a common name on the process list. +I would start this program using the following command: `./monitor iw5`. It will monitor all my game servers as they all share a common name (iw5) on the process list. In my case, each process should not exceed more than 1 GiB of real memory, again, the max value is defined in `monitor.c`. If that's the case, a memory leak has occurred, and this program will send a request to terminate that process gracefully (SIGTERM). SIGTERM usually works for me. I have in place a separate system to automatically restart my game servers.