Next: check_interfaces | Previous: spongtoc | [Table of Contents] | [Index] |
./build <os
> where <os> is the name corresponding to your
operating system. You can type ./build help
to generate a list of
valid operating system strings.
When the build completes, you will be left with some new directories in the folder that you unpacked spong in. The build process takes the spong source (and documentation), and replaces some "tokens" with values that you have supplied at the top of the build script. The build process also creates a spong.conf file, and generates various types of documentation based on the POD files that come with spong.
./build install
. Note that the install process makes
no assumptions about what user you want to run spong as (you don't
have to run it as root). This means that you have to be a little more careful
when you install spong (making sure it has the correct permissions, and
that you have permission to copy the www pages into your web server's document
tree).
NOTE - HOSTNAMES: Part of spong-server's status message authentication has to do with host names. spong-server checks the host name in a status message against the hosts defined in the spong.hosts file. The the status message host name is not found, spong-server will silently drop the messages.
So it is important that your serves are able to resolve their fully qualified
domain name. To do this check there is a little Perl test program
gethost-test from in the /utils
directory of the Spong distribution. Just
run it from a command line by entering perl gethost-test.
It tests to see is
the host can resolve it's fully qualified domain name. If it can't then it
will advise you on ways to fix the problem. See also Question 2 in the Admininistration Guide.
./build install
step
is done, you can remove a number of directories that are not needed by
spong-client. (Assuming a standard installation directory).
etc/spong.conf
(and
etc/spong.conf.>host>
files(s).
If you have a number of like clients with the same OS your can copy the entire installation directory tree from an installed client to other clients. You can use tar+ftp, rcp, rdist or whatever mechamism you would normally use. Just be sure the Spong installation directory into the same location as the original client.
http://www.example.org/spong/cgi-bin/www-spong
, you need to set $WWWSPONG
to '/spong/cgi-bin/www-spong'. See also the section on SPONG CGI DIR elsewhere in this document.
http://www.example.org/spong/cgi-bin/www-spong-ack
, you need to set
$WWWSPONG to '/spong/cgi-bin/www-spong-ack'. See also the section on SPONG CGI DIR elsewhere in this document.
http://www.example.org/spong/gifs/
, then $WWWGIF is set to '/spong/gifs'.
See also the section on Spong HTML Directory elsewhere in this document.
SPONG/www/html
direcotyr
on the file system. The Web Display programs reads the requested files, does
some token replacement, and send the files to the web server.
SPONG/www/docs
directory
on the file system. The Web Display programs reads the requested files, does
some token replacement, and send the files to the web server.
SPONG/www
directory and the SPONG/cgi-bin/
CGI directory
SPONG/cgi-bin/
directory must be setup as a CGI directory and aliased
into the desired location. For example, for Apache a sample configuration
line would be:
ScriptAlias /spong/cgi-bin/ /usr/local/spong/cgi-bin/
SPONG/www/
directory must be aliased into the desired location within
the web server document tree. If you want the SPONG/www
directory
to be under http://www.example.org/spong/ on an Apache web server, use this
configuration line:
Alias /spong/ /usr/local/spong/www/
ps
command.
If $SPONG_LOG_FILE or $SPONG_LOG_SYSLOG are set in the spong.conf
file
the programs will log errors to a log file and/or syslog , respectively. The
file are named program-name.log
in the $SPONGTMP directory and the
entries are logged to syslog under the USER facility with a priority of ERR.
When spong-server is run with --debug # the primary process will run in the fore-ground and all of the child processes with write their debugging statements to the screen. The query processing will print out all of the database queries with the type of data requested and in what format. The spong update and Big Brother update process will print out host/service/color of every status message that is received.
The update processes will print out their actions concerning notifications. If a notification is indicated, spong-server will call spong-message with the --debug parameter if --debug was specified in the command line.
spong-message --debug color host service time "Summary message"where:
After the rules matching phase, spong-message will then print out all of the people being notified and how they are being notified. spong-message can potentially print out a large quantity of debugging. You may want to redirect the output to a file while you are testing it.
/html
directory where the
Spong www/ directory was installed (the $IWWW variable from the build
program) and named "header.html" or "footer.html", respectively.
Place the HTML code that you want display into the template files. You can also specify other HTML files to be included when the file is display. Insert the string "!!WWWSHOW!!/filename" into the place that your desire the file named "filename" to be display. The file to be include should placed into the same directory are the "header.html" or "footer.html" file resides.
Note: This customization feature is limited in the current release. More substitution variables (i.e. hostname, service, status, etc) will be added into future. As will the ability to select which type of pages the headers or footer will be placed (i.e. service status screen, server display screen, history screen, problem screen, etc.)
spong-server first looks for a info.brief, info.standard or info.full file
depending on the type of display (brief, standard or full; and html or txt). If
the program finds one it will display that file. Otherwise, spong-server
will look for a info.txt
or info.html
file and then display that file as
a default.
The .txt files are used with text mode displays like those generated by the spong display command (see the spong manpage). The .html files are used by the html mode displays. The .html files can contain html code, URLs, embedded graphics, Javascript, or anything that you display on a web page.
The "Contact Staff" link URL consists of two parts. The first part is the
$WWWCONTACT from the spong.conf
configuration file (see
the section on $WWWCONTACT in the spong.conf manpage). It contains the URL to your contact
staff CGI program that you must supply (see below). The second part of the are
the host name and the problem message passed as two form variables: host
and message respectively.
The $WWWCONTACT CGI program needs to handle two form variables (host and message) and a couple of fields on a form for the user to fill out. A TEXT field should be used to the host variable with a size of 50 characters of so to handle big host names. The message field should be placed in a TEXT AREA field. The size of the TEXT AREA field should be limited if the destinations are pager. Most alpha-pages have a message limit of 150-250 characters. The rest of the form should be populated with whatever fields that you need into order to interface to your paging applications
This parameter is preprocessed with the Perl eval
function before the
contents are printed. This allows you to include complex perl variables or perl
code. Because of the eval
processing you should use single quotes to enclose
the contents of this parameter. This will prevent premature evaluation of perl
variables before the output.
If your do not need this customization, just leave $WWW_ACTIONBAR_CUSTOM undefined. Nothing will be added to the Action Bars.
For example, if @WWW_REFRESH_ALLOW contains[ 'joe', '.*-support', '^192.168.12.*', 'noc-display' ] and @WWW_REFRESH_DENY contains ['bill','mary']. If a web brower on a machine at ip address 192.168.12.143 queries the spong-server web pages, the auto-refresh would be allowed because it matches the '^192.168.12.*' expression of @WWW_REFRESH_ALLOW. But if the user was 'fred' at the same machine (192.168.12.143), auto-refresh would not be enabled because 'fred' is in the I@<WWW_REFRESH_DENY> list.
sjohnson@monsters.org
>