The rest of the form should be populated with whatever field that you need
into order to send your messages.
<br>
+
+<h2><a NAME="custom-actionbar"></a>Customized Action Bar</h2>
+The Action Bar of the Host and Service Status Displays (see the
+<a href="user-guide.html">User Guide</a> for more details) can be customized
+with the <a href="spong_conf.html#custom-actionbar"><b>$WWW_ACTIONBAR_CUSTOM
+</b></a> configuration parameter. Any HTML code defined in this parameter
+will be included on the end of the Action Bars.
+
+<p>This parameter is preprocessed
+with <i>eval</i> before the contents are printed. This allows you to
+include complex perl variables or perl code. Because of the <i>eval</i> you
+should use single quotes to enclose the contents of this parameter. This
+will prevent premature evaluation of perl variables before the preprocessing.
+
+<p>If your do not need this customization, just leave
+<b>$WWW_ACTIONBAR_CUSTOM</b> undefined. Nothing will be added to the Action Bars.
+
+
<h2>
<a NAME="autorefresh"></a>WWW_REFRESH LOGIC</h2>
The default of the spong-server is to not allow auto-refreshes if <b><a href="spong_conf.html#www-refresh-allow">@WWW_REFRESH_ALLOW</a></b>
being displayed. for more information on this feature, please see the <a href="admin-guide.html#custom-contacts">Administrator
Guide</a>.</dd>
+<dt><A NAME="custom-actionbar"></a><b>$WWW_ACTIONBAR_CUSTOM<b>
+
+<dd>
+This parameter can be used to customize the Host/Service displays Action Bar
+of the Web Interface. Any HTML code in this parameter will be included on
+the Web Pages when they are displayed. This parameter is preprocessed by
+<I>eval</i>'ed before the contents is printed. Your can include complex
+perl variables and simple Perl code in this parameter. NOTE: Use single
+quoted to enclose the parameter contents to prevent premature expansion of
+any perl variables defined.
+</dd>
+
<dt>
<a NAME="www-refresh-allow"></a><b>@WWW_REFRESH_ALLOW</b></dt>
<br> </dl>
+<hr>
+<h1><a name="spong-cleanup"></a>SPONG CLEANUP VARIABLES
+
+<dl>
+<dt><b>$SPONG_ARCHIVE</b>
+
+<dd>
+The directory where to put old history file entries for each host. Each host have it's own file in this directory
+</dd>
+
+<dt><b>$OLD_HISTORY</b>
+
+<dd>This is the number of days of history to keep for each host in the
+spong-server database. Any old history is append to the file for the host under
+the <b>$SPONG_ARCHIVE</b> directory.
+</dd>
+
+<dt><b>$OLD_SERVICE<b>
+
+<dd>This is the number of days to retain stale service status (i.e. purple
+status) entries in the spong-server database. Any service service status
+entries older than <b>$OLD_SERVICE</b> days old are deleted from the
+database.
+</dd>
+
+</dl>
+
<hr>
<h1>
<a NAME="service-threshold"></a>SERVICE THRESHOLD VARIABLES</h1>
-<html>\r\r
-<head>\r\r
-<title>Spong v1.1 - Todo List</title>\r\r
-</head>\r\r
-<body>\r\r
-\r\r
-<h1>Spong v1.1 - Todo List</h1>\r\r
-<hr>\r\r
-\r\r
-Here are the features/changes that I want to make to spong. They are in no\r\r
-particular order, but I will probably be working on the things at the top of\r\r
-this list before I get to the ones on the bottom. If you have any suggestions\r\r
-or comments, send email to <a\r\r
-href="mailto:ed-hill@uiowa.edu">ed-hill@uiowa.edu</a>. I have no specific time\r\r
-schedule in mind for implementing this list. Spong is now a night-time\r\r
-project, so I get to this things when I can.<p>\r\r
-\r\r
-I have put *'s next to the items that I am currently working on - or have\r\r
-completed in cased you are curious about my progress.<p>\r\r
-\r\r
-<ul>\r\r
-<li>(*) Rework some of the design of spong to make things more object oriented.\r\r
-The first version of spong was basically a port of BB, version 2.0 will be\r\r
-different. This will allow me to more easily integrate new features over time.\r\r
-\r\r
-<li>(*) Add nfs (and other rpc based services) to spong-network (using the\r\r
-rpcinfo command).\r\r
-\r\r
-<li>Client support (spong-client) for NT\r\r
-<li>Server support (spong-server, spong-network, spong-display) support for NT\r\r
-\r\r
-<li>(*) Provide different interfaces (currently only web - provide a PerlTk,\r\r
-and a terminal based interface).\r\r
-\r\r
-<li>Provide the ability to view spong information (run the spong, tkspong, and\r\r
-wwwspong (currently known as spong-display) programs from machines other then\r\r
-the spong server).\r\r
-\r\r
-<li>(*) Redo the web based spong-display to make it more extensible\r\r
-<ul>\r\r
-<li>Allow people to easily put the spong-server CGI program in /cgi-bin/\r\r
-<li>Allow people to easily define their own interfaces\r\r
-<li>Allow people to easily include parts of spong-display.cgi output in\r\r
-other pages\r\r
-<li>Allow for multiple views (table, network diagram, simple host summary\r\r
-with drill down for more specific information)\r\r
-<li>Handle groups better.\r\r
-\r\r
-</ul>\r\r
-\r\r
-<li>Provide a rules based solution to sending pages - this will allow people to\r\r
-specify whatever rules they want for sending pages when there are problems.\r\r
-\r\r
-<li>(*) Add acknowledgements - so that you can say that you know a service is\r\r
-red - and that you don't want paged about it. You can also add some text so\r\r
-that others reading spong can have an idea what the problem is, and know\r\r
-someone is working on it.\r\r
-\r\r
-<li>Make spong-network more parallel, have it perform checks from a pool of\r\r
-children, that way if a system can not be pinged - it will not slow up the rest\r\r
-of the checks.\r\r
-\r\r
-<li>Make spong-network check more often on hosts that do not respond on the\r\r
-first try\r\r
-\r\r
-<li>Optimize the communication between client and server - by pipelining\r\r
-reports through a single channel and perhaps compressing the data before\r\r
-sending it.\r\r
-\r\r
-<li>Fix the log file checking - make it smarter.\r\r
-\r\r
-<li>Make it so that you can click on a host and find out status, history, \r\r
-configuration (inventory), and statistics. (starting to branch out).\r\r
-<ul>\r\r
-<li>Integrate my gstats (statistics collection) program. "spong-stats"\r\r
-<li>Add an inventory/configuration module. "spong-config"\r\r
-</ul>\r\r
-</ul>\r\r
-<hr>\r\r
-Most recently updated on May 8, 1997 by\r\r
-<a href="http://strobe.weeg.uiowa.edu/~edhill/">Ed Hill</a>\r\r
-(<a href="mailto:ed-hill@uiowa.edu">ed-hill@uiowa.edu</a>)\r\r
-</BODY>\r\r
-</HTML>\r\r
+<html>\r
+<head>\r
+<title>Spong v1.1 - Todo List</title>\r
+</head>\r
+<body>\r
+\r
+<h1>Spong - Todo List</h1>\r
+<hr>\r
+\r
+Here are the features/changes that I and others want to make to spong. They\r
+are in no particular order, If you have any suggestions or comments, send\r
+email to <a href="mailto:sjohnson@monsters.org">sjohnson@monsters.org</a>. <p>\r
+\r
+<ul>\r
+\r
+<li>Make web interface more configurable: (user selectable backgroup colors/\r
+method, table shading scheme)\r
+\r
+<li>Add option to use style sheets on Web Interface.\r
+\r
+<li>Client support (spong-client) for NT\r
+<li>Server support (spong-server, spong-network, spong-display) support for NT\r
+\r
+<li>Make spong-network more parallel, have it perform checks from a pool of\r
+children, that way if a system can not be pinged - it will not slow up the rest\r
+of the checks.\r
+\r
+<li>Make spong-network check more often on hosts that do not respond on the\r
+first try\r
+\r
+<li>Optimize the communication between client and server - by pipelining\r
+reports through a single channel and perhaps compressing the data before\r
+sending it.\r
+\r
+<li>Make it so that you can click on a host and find out status, history, \r
+configuration (inventory), and statistics. (starting to branch out).\r
+\r
+<li>Integrate my gstats (statistics collection) program. "spong-stats" (Ed Hill)\r
+<li>Add an inventory/configuration module. "spong-config"\r
+\r
+<li>Continue modularizing to move towards Object Oriented as much as possible.\r
+\r
+<li>Add control ports to spong-client,spong-network, and spong-server to\r
+ultimately allow the programs to be control and configured remotely\r
+\r
+</ul>\r
+<hr>\r
+Most recently updated on Dec. 6, 1999 by\r
+Stephen L Johnson\r
+(<a href="mailto:sjohnson@monsters.org">sjohnson@monsters.org</a>)\r
+</BODY>\r
+</HTML>\r