
#
# Copyright (c) Xerox Corporation 1997, 1998. All rights reserved.
#
# License is granted to copy, to use, and to make and to use derivative
# works, provided that Xerox is acknowledged in all documentation
# pertaining to any such copy or derivative work. Xerox grants no other
# licenses expressed or implied. The Xerox trade name should not be used
# in any advertising without its written permission.
#
# XEROX CORPORATION MAKES NO REPRESENTATIONS CONCERNING EITHER THE
# MERCHANTABILITY OF THIS SOFTWARE OR THE SUITABILITY OF THIS SOFTWARE
# FOR ANY PARTICULAR PURPOSE.  The software is provided "as is" without
# express or implied warranty of any kind.
#
# These notices must be retained in any copies of any part of this software.
#



INSTALLING THESE PROGRAMS AT YOUR SITE:

The route monitor package install program should correctly install all
programs and set any locally dependent values.

In the event the install program failed or if you are not using the install
program, be sure to follow these guidelines:

0) first complete the install instructions for ../html, ../routemonitor, and
   ../cgi

1) Copy htmlmaker, aslookup, asretry, and statsedit into an appropriate 
   directory for executables.  (recommended you chose the executable directory 
   selected when you installed ../routemonitor)

2) Edit htmlmaker, aslookup, asretry, and statsedit and replace FOOPERL with 
   the location of perl v5.0 or higher.

3) Edit htmlmaker and replace FOORTEMONDIR with the directory where 
   the routemonitor program will write its output. (you chose this
   directory when installing ../routemonitor)

4) Edit htmlmaker, aslookup, asretry, and statsedit and replace FOOHMKRDIR 
   with a directory in which you would like htmlmaker to write working files.
   It is strongly recommended that you make this the same as the FOORTEMONDIR
   directory chosen in step 3.

5) Edit htmlmaker, asretry, and statsedit and replace FOOWEBDIR with the 
   directory where html files are to be written.  (you chose this directory 
   when installing ../html).

6) Edit htmlmaker and replace FOOARDIR with a directory in which you would
   like htmlmaker to store any route table or route statistics archives.
   htmlmaker will store archive files for each table, weekly stats, and/or
   monthly stats if run with the -T,-W, or -M option.  (see the htmlmaker man
   page)

7) Edit htmlmaker and replace FOORTEEXEC with the complete path for the
   routemonitor executable.  htmlmaker will automatically start routemonitor.

8) Edit htmlmaker and replace FOOASLEXEC with the complete path for the
   aslookup executable. htmlmaker will periodically launch aslookup.

9) Finally, replace FOOCGISEARCH with the complete URL for the rmsearch
   cgi script, ie http://www.mysite.edu/mycgidir/rmsearch.

10) Review the man page for htmlmaker and launch the entire RouteMonitor
    package by simply running htmlmaker.
 


If you need additional help or to report bugs, send mail to masseyd@cs.ucla.edu
   
