#!FOOPERL

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



#----- default directory names and executable paths ----------
# users can override these values using the command line options listed
# the output directory for the route monitor program, command line opt -d
$rtemondir = "FOORTEMONDIR";
# the executable for the route monitor program, command line opt -E
$rtemon = "FOORTEEXEC";
# the output directory for the as lookup program, command line opt -l
$aslookupdir = "FOOHMKRDIR";
# the executable for the as lookup program, command line opt -L
$aslookup = "FOOASLEXEC";
# the output directory for this program, command line opt -h
$hmakerdir =  "FOOHMKRDIR";
# the directory to put new web pages, command line opt -w
$webdir = "FOOWEBDIR";
# the directory to archive any route table or route stats, command line opt -a
$archivedir = "FOOARDIR";
# the complete href to the associated cgi search script, command line opt -s
$search_cgi = "FOOCGISEARCH";
# no modifications should occur below this point

#-----------------------------------------------
# command line options
# option: -r rtr
#   action: instruct route monitor to only accept route updates from rtr
#   default: route monitor accepts updates from all neighboring routers
# option: -x
#   action:  instruct route monitor to always dump the route table on exit
#   default: route monitor only dumps the route table only when signaled
# option: -d directory
#   action: instruct route monitor to use the output directory for all output
#   default: route monitor uses its default directory for all output
# option: -e executable
#   action: instruct route monitor to run the routewatch program executable
#   default: route monitor runs its default routewatch program
# option: -E executable
#   action:  run route monitor program executable
#   default: run the route monitor program $rtemon defined above
# option: -l directory
#   action: instruct aslookup to use the output directory for all output
#   default: aslookup uses its default directory for all output
# option: -L executable
#   action:  run as lookup program executable
#   default: run the as lookup program $aslookup defined above
# option: -h directory
#   action: write pid file and error log to directory
#   default: write pid file and error log to $hmakerdir defined above
# option: -w directory
#   action: write the html files generated to directory
#   default: write the html files generated to $webdir defined above
# option: -s href
#   action: use href as the hyper link to the cgi search script
#   default: use $search_cgi above as the href (used in week/month html files)
# option: -a directory
#   action: write any route tables or route stats archived to directory
#   default: write any route tables or stats archived $archivedir defined above
# option: -W
#   action: archive the route statistics each week
#   default: do not archive route statistics weekly
# option: -M
#   action: archive the route statistics each month
#   default: do not archive route statistics monthly
# option: -T
#   action: archive each route table generated by route monitor
#   default: do not archive any route tables generated by route monitor
# option: -R script
#   action: run script to copy the html files generated to a remote web server
#   default: web server directories are locally accessible
#  NOTE: this option should be used by sites where this program can not
#  directly write to a web server area.  The script specified with -R
#  should use rcp or ftp or any other method to copy all the files from
#  $webdir onto the web server.  The script will be run by this program
#  each time new files are generated in $webdir


