[Sysfence-commit] sysfence/doc example.conf,1.7,1.8

[Michal S. <em...@us...>]

Update of /cvsroot/sysfence/sysfence/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv30765/doc

Modified Files:
	example.conf 
Log Message:
+ updated info files, preparing to make next release


Index: example.conf
===================================================================
RCS file: /cvsroot/sysfence/sysfence/doc/example.conf,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- example.conf	26 May 2004 17:52:13 -0000	1.7
+++ example.conf	29 May 2004 16:42:05 -0000	1.8
@@ -1,12 +1,6 @@
 #
 #   This is example configuration file for sysfence
 #
-#
-#   ** WARNING! **
-#
-#       The 'log' option described here, doesn't work yet.
-#
-#
 #   - Config file consists of rules.
 #   - Each rule has condition part and action part.
 #   - Condition is enclosed in block.
@@ -15,7 +9,7 @@
 #   Here is an example:
 #
 
-if {
+rule "high load" {
    la1 >= 5.0 and
    {
        { la5 > 3.0 and la5 < 5.0 }
@@ -30,12 +24,17 @@
 #   Notice the 'once' keyword. You may use it right after 'run' or 'log'.
 #  It means that run/log action will take place only once after condition
 #  becomes true.
+#
 #   In example above, echo command will be run once when system load exceeds
 #  given thresholds, but logging will be performed periodically unless load
 #  falls below limits.
+#
 #   If the load falls (making condition false) and then rises again, the echo
 #  command will be invoked as well.
 #
+#   Log entry will contain rule name (the string right after rule keyword)
+#  and current value of all stats checked in condition.
+#
 #   The values you may check, are:
 #
 #       la1         - system load during last minute
@@ -45,9 +44,12 @@
 #       usedmem     - used memory (w/o disk cache)
 #       freeswap    - free swap space
 #       usedswap    - used swap
+#       freespace   - free disk (or other fs-device)  space
+#       usedspace   - used disk space
+#       availspace  - available disk space (free - space reserved for superuser)
 #
 
-when {
+when "memory low" {
    freemem < 128M
    or
    swapused > 256M
@@ -65,12 +67,23 @@
 #       run         invoke      exec        execute
 #       once        onlyonce
 #       step        stepping
+#
+# for load:
 #       la1         load1       loadavg1    (same with 5 and 15)
+#
+# for memory:
 #       memfree     freemem     freememory
 #       usedmem     memused     usedmemory
+#
+# for swap:
 #       swapfree    freeswap
 #       usedswap    swapused
 #
+# for filesystem:
+#       spaceused   usedspace
+#       spacefree   freespace
+#       spaceavail  availspace  spaceavailable availablespace
+#
 #   ...and operators:
 #
 #       =   ==
@@ -81,17 +94,6 @@
 #       and     andalso     &&
 #       or      orelse      ||
 #
-#
-#   With many rules defined, you can get easily confused while reading logs.
-#   To make things clear, you may give rule a name, putting it right after
-#   if keyword (or it's synonyme). It will appear in log entries.
-#
-
-rule "this machine works hard" {
-    la15 >= 3.0
-} log
-
-#
 #   Good luck!
 #
 # $Id$