[Mon-commit] mon/doc mon.8,1.1.1.1,1.1.1.1.2.1

[Jim T. <tr...@us...>]

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

Modified Files:
      Tag: mon-1-0-0pre1
	mon.8 
Log Message:
added 'alertevery strict' code and docs, updated the README and INSTALL to mention CVS, updated CREDITS

Index: mon.8
===================================================================
RCS file: /cvsroot/mon/mon/doc/mon.8,v
retrieving revision 1.1.1.1
retrieving revision 1.1.1.1.2.1
diff -C2 -d -r1.1.1.1 -r1.1.1.1.2.1
*** mon.8	9 Jun 2004 05:18:06 -0000	1.1.1.1
--- mon.8	17 Jun 2004 20:28:54 -0000	1.1.1.1.2.1
***************
*** 363,367 ****
  .I unless
  the summary output from the current monitor program differs from the last
! monitor process. Otherwise, send an alert using each alert program
  listed for that period. The
  .B "observe_detail"
--- 363,368 ----
  .I unless
  the summary output from the current monitor program differs from the last
! monitor process.
! Otherwise, send an alert using each alert program
  listed for that period. The
  .B "observe_detail"
***************
*** 376,379 ****
--- 377,387 ----
  The reasoning is that if the summary output changes, then
  a significant event occurred and the user should be alerted.
+ The "strict" argument to alertevery will suppress both
+ comparing the output from the previous monitor run to the current
+ and prevent a successful return value of the monitor from
+ resetting the alertevery timer. For example, "alertevery 24h strict"
+ will only send out an alert once every 24 hours, regardless of
+ whether the monitor output changes, or if the service stops and then
+ starts failing.
  
  .SH ALERT\ PROGRAMS
***************
*** 1113,1117 ****
  
  .TP
! .BI alertevery " timeval [observe_detail]"
  The
  .B alertevery
--- 1121,1125 ----
  
  .TP
! .BI alertevery " timeval [observe_detail | strict]"
  The
  .B alertevery
***************
*** 1135,1139 ****
  "observe_detail" is the last argument, then both the summary
  and detail output lines will be considered when comparing the
! output of successive failures. Please refer to the
  .B "ALERT DECISION LOGIC"
  section for a detailed explanation of how alerts are suppressed.
--- 1143,1152 ----
  "observe_detail" is the last argument, then both the summary
  and detail output lines will be considered when comparing the
! output of successive failures.
! If the string "strict" is the last argument, then the output
! of the monitor or the state change of the service will have
! no effect on when alerts are sent. That is, "alertevery 24h strict"
! will send only one alert every 24 hours, no matter what.
! Please refer to the
  .B "ALERT DECISION LOGIC"
  section for a detailed explanation of how alerts are suppressed.