#
# 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:

1) Compile the routewatch.c program to produce an executable: routewatch

2) Copy routemonitor, routewatch, dump_table, and reset_table into an
   appropriate directory for executables.

3) Change the permissions on routewatch so that it runs at setuid to root

4) Edit routemonitor and replace FOORWEXEC with the complete path for
   the routewatch executable (ie if routewatch was in /usr/local/bin,
   FOORWEXEC should be replaced by /usr/local/bin/routewatch)

5) Edit routemonitor, dump_table, and reset_table.  Replace FOORTMDIR
   with the directory in which you would like routemonitor to write
   its output files.  Replace FOOPERL with the location of perl version 5.0
   or higher.
   *** routemonitor output files include an error log, pid file, and
       route table dumps
   *** if a route monitor configuration file is used, the file 
       route_monitor.conf must also go in this directory (see step 6 below)

6) OPTIONAL:  install the route monitor configuration file.
   by default, the route monitor assumes the cost to reach each neighboring
   router is 1.  If you wish to assign different costs/metrics to neighboring
   routers or links, copy the file route_monitor.conf into the FOORTMDIR
   chosen in step 5.  Edit the route_monitor.conf file, following the
   instructions in that file to assign costs to neighboring links/routers.


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