From d650fb6316e64acece58acf1c99ea3adbc32e1c7 Mon Sep 17 00:00:00 2001 From: Faiyaz Ahmed Date: Tue, 25 Sep 2007 19:12:02 +0000 Subject: [PATCH 1/1] Updated Readme --- README.txt | 19 +++++-------------- 1 file changed, 5 insertions(+), 14 deletions(-) diff --git a/README.txt b/README.txt index cf11831..8187d5f 100644 --- a/README.txt +++ b/README.txt @@ -5,26 +5,17 @@ Overview much memory, and by rebooting the machine once the swap space is nearly full. -Specifically, pl_mom takes the following actions based on the amount +Specifically, swapmon takes the following actions based on the amount of consumed swap space: -* at 85% full, pl_mom starts logging the available swap space to - syslogd +* at 80% full, swapmon starts logging the available swap space to + syslogd, restart largest slice and send mail. -* at 90% full, pl_mom resets the slice that is consuming the most - physical memory and sends an alert mail to that slice and the pl-mom - alias + After 3 restarts, kill slice. -* at 95% full, pl_mom reboots the machine and sends mail to the pl-mom +* at 95% full, swapmon reboots the machine and sends mail to the pl-mom alias -Pl_mom is organized as two processes. The reboot process runs every -second, and the slice reset process runs every 30 seconds. The reboot -process is very lightweight and only reads /proc/swaps. However, the -slice reset process may pull data from the slicestat sensor on port -3100, which can potentially take a long time (on the order of minutes -if there are thousands of processes on the machine). - Building --------- -- 2.45.2