documentation updates

diff --git a/pod/spong.conf.pod b/pod/spong.conf.pod
index b6d6679572dbaa4f97279bbe8b295fc981c34d94..d2365b2843df167e7aedf86d255bf63786f3aaab 100644 (file)
--- a/pod/spong.conf.pod
+++ b/pod/spong.conf.pod
@@ -37,10 +37,22 @@ will fall back to using $SPONGSLEEP.
 
 =item $SPONGSERVER 
 
-The host that at least the L<spong-server> and L<spong-message>
+The host that, at the least, the L<spong-server> and L<spong-message>
 programs are running on. Typically the L<spong-network> program runs on that
 host as well.
 
+Multiple hosts can now be specified in <$SPONGSERVER>. This allows you to run
+mutiple Spong Server instances for multiple monitored domains, and eventually
+High Availability functionality.
+
+The fully syntax is:
+
+   spong-server1.example.com[:port] [spong-server2.example.org[:port] ...]
+
+The '[:port]' specified the port the update process is listening on for that
+Spong Server. See L<$SPONG_UPDATE_PORT> for more information. The default value
+is 1998.
+
 =item $SPONG_UPDATE_PORT
 
 This variable defines the port that the L<spong-server> update process listens

diff --git a/pod/spongfaq.pod b/pod/spongfaq.pod
index 70823263104a149698f18e30f0777e8821156341..71f6b278816068e75f7983874b376b3c25fb7529 100755 (executable)
--- a/pod/spongfaq.pod
+++ b/pod/spongfaq.pod
@@ -1,6 +1,6 @@
 =head1 NAME
 
-spongfaq - frequently asked questions about Spong ($Revision: 1.3 $, $Date: 2000/12/21 22:47:56 $)
+spongfaq - frequently asked questions about Spong ($Revision: 1.4 $, $Date: 2001/01/05 20:50:01 $)
 
 =head1 DESCRIPTION
 
@@ -121,9 +121,9 @@ This will send everything to the 'sjohnson' contact.
 
 =item 1. %HUMANS in spong.hosts
 
-In spong.hosts, you must define at least one contact (the %HUMANS in spong.hosts)
-in order to have any notifications sent. for the example rule setup above,
-to get e-mail sent to that user you can have an entry like:
+In spong.hosts, you must define at least one contact (the %HUMANS in
+spong.hosts) in order to have any notifications sent. For the example rule
+setup above, to get e-mail sent to that user you can have an entry like:
 
    %HUMANS = (
       'sjohnson' => {
@@ -174,6 +174,21 @@ The time is in 24 hour format and the year is the 4 digit year. This will
 print a large number. Use the number in place of the back-ticked perl 
 expression on spong-message command.
 
+=item 1. Testing with spong-server
+
+The best way to test everything to set $SEND_MESSAGE to 'CHANGE' and run
+spong-server in debug mode with a debug level of at least 3 (i.e. spong-server
+--debug 3 ). This will cause spong-server to call spong-message for every
+chagne in status of any host . And spong-server will call spong-message in
+debug mode also. This will let you see everying that spong-server and
+spong-message is doing. You will see spong-server say something like "change in
+state to red messaging a human." in it's debug output when it is sending out
+notifications.
+
+Once you have your single contact / single messaging rule configuration
+working.  Change $SEND_MESSAGE to what you desire. And then start adding in
+more messaging rules and contacts. But continue testing your spong.message
+config file as described above (see "Testing Messaging Rules").
 
 =back