$Avoid:  A regex (regular expression) identifying any particular files
that you don’t wish to be examined for links.  Other files which link
to these files will still list them in their “links to” lists, but the
files identified in this variable will not be listed independently,
and will not show up on your site map.

$ParseCGI:  A regex identifying any CGI scripts which you want to have
parsed.  If left undefined, the existence of any CGI scripts will be
noted, but they won’t be run.  (Generally, that will be what you want
to do.)  However, if you have CGI scripts which generate actual pages
which you want included in the site map, note them in this variable.

$ListBinaryLinks:  If you wish binary files (graphics, .zip files, etc.)
to be excluded from the “links to” lists, set this variable to “0″;
otherwise, leave it set to “1″.  If you have a lot of navigation
buttons which appear on every page, for example, setting this flag
to “0″ can help reduce the size of your report.

$MissingLinks:  If this variable is set to “1″ the script will tell you
about files which exist but are not referenced.  If it is set to “0″
the information will not be included.  (This is useful if your
directory structure contains a large number of files unrelated to
your Web site.)

$IgnoreExternals:  If this variable is set to “1″ the script will not
check the validity of external links.  If it is set to “0″ it will
check them.  Note that this can take a significant amount of time if
you have a lot of links!

$ShowOnlyErrors:  If this variable is set to “1″ the “site check” report
will only tell you about problems.  If it is set to “0″ the report
will tell you about everything.

$PrintDates:  If you set this variable to “1″, your site map will
include the date on which each listed file was last modified.

$DaysNew:  If you define this variable with a positive number of days,
any file listed in the site map which was modified more recently will
be flagged as “NEW!”  For example, if the $DaysNew variable is set to
“7″, and file which has been modified (or created) within the past
week will be so flagged.  Note that the $PrintDates and $DaysNew
flags are independent; your site map can show dates, “NEW!” flags,
both or neither, as you prefer.

$MinLevel:  This variable allows you a bit of control over how your site
map is constructed, by allowing you to specify that certain files
won’t appear too high in the hierarchy.  The index file is level 1,
files referenced by it are level 2, files referenced by them are level
3, etc.  The “minimum level” for a particular file is the highest
level at which it is allowed to appear on the map.  (For example, if
file “/usr/foo/document.html” is referenced from your main index page,
but you want it to appear on the map under your news and information
page, which also references it, you could set its minimum level to
“3″ and thus insure that it won’t appear at level 2.)  You can also
specify that certain files won’t appear on the map at all, simply
by giving them very high minimum levels.

$Verbose:  Setting this variable to “1″ will instruct the script to
provide you with “status” comments as it runs.  Setting it to “0″
will disable the comments.  Any error messages, of course, will still
be generated.

$URL_Timeout:  The number of seconds that the script should wait for a
response when checking external URLs.  If the server hasn’t responded
when the time limit expires, the report will display on the list of
failed external URLs simply that it was “unable to connect” to the
site.  By default, this variable is set to 20 seconds.

$getpwd:  The command on your server for retrieval of the “current”
file path.  On Unix systems, this command is “pwd”; that is what
is used by the script if this variable is undefined.

$gethostname:  The command on your server for retrieval of the host
name.  On Unix systems, this command is “hostname”; that is what
is used by the script if this variable is undefined.

This documentation assumes that you have at least a general familiarity
with setting up Perl scripts.  If you need more specific assistance,
check with your system administrators, consult the WebScripts FAQs
(frequently-asked questions) file <http://awsd.com/scripts/faqs.shtml>,
or ask on the WebScripts Forum <http://awsd.com/scripts/forum/>.