Having problems with CGI scripts for my website

=head1 INSTALLATION
 
1. Copy the file C<script.pl> to C<cgi-bin> directory of your website, give it a
name of your choice and set permissions on the file:
 
  $ cp script.pl /path/to/cgi-bin/whatever_name.pl
  $ chmod 755 /path/to/cgi-bin/whatever_name.pl
 
2. The password file (C<.htpasswd>) will be stored in so-called data directory
on your website. Either use already existing directory or create a new one and
set permissions on this directory.
 
  $ mkdir /full/path/to/your_data_dir
  $ chmod 770 /full/path/to/your_data_dir
 
3. Copy all files from C<data> directory in the distribution file to your newly
created data directory.
 
  $ cp data/* data/.* /full/path/to/your_data_dir
 
4. Edit the script and change value of C<$prefix> variable to the name of your
data directory (including full path).
 
5. [Optional] You can modify other variables in the configuration area to better
suit your needs.
 
6. Modify C<.htaccess> file in protected area of your website. This file
specifies location of your password file. It should contain line like
 
  AuthUserFile /home/xxxxxxx/data/.htpasswd
 
7. Visit Verotel Control Center and test your RUM setup by trying to add user
account. Check that the added test user account allows you to access protected
area of your website. Try to delete this user account and check access to the
protected area isn't possible for this user anymore.
 
8. If your RUM setup works fine, please submit a test request so a Verotel
Engineer can test your installation. If your RUM setup doesn't work, please
submit an installation request, and a Verotel Engineer will perform the
installation for you at no cost.
 
=head1 CONFIGURATION
 
Keep the configuration files in directories invisible to users browsing your
website. The actual physical location of the files doesn't matter as long as
ordinary users don't have access to them.
 
=head2 $prefix
 
This is the data directory which contains the password file, log file and other
supporting files.
 
Replace default value in C<$prefix> with full path to data directory on your
website. To prevent ordinary users from accessing the directory and files
inside, you should set proper file permissions on them.
 
  $ chmod 770 /full/path/to/your_data_dir
 
=cut
 
our $prefix            = '/home/xxxxxx/data';
 
=head2 $ip_file
 
To make sure only Verotel servers can call this script, caller's IP address is
checked against list of trusted IP addresses and only connections from IP
address found on this list are allowed. This list is stored in
C<$ip_file>.
 
IP addresses are stored one per line, in IP/mask (C<A.B.C.D/dd>) format.  Mask
is a number between 1 and 32 (inclusive) and defines network mask length in
bits. Bit mask length of 32 defines single IP address, shorter masks define IP
address ranges (subnets).
 
Current Verotel IP range is C<195.20.32.128/25>.
 
Don't forget to set proper file permissions to prevent ordinary users from
reading or writing the file:
 
  $ chmod 660 /home/xxxxxx/data/.ht_IP_addresses
 
=cut
 
our $ip_file           = "$prefix/.ht_IP_addresses";
 
=head2 @file_config
 
Specify locations of C<htpasswd> files, along with their respective log files.
C<@file_config> consists of <password file - log file> pairs. Most people
will only need one such pair, but should you need the accounts to be mirrored
across several websites, you can list as many pairs as you want.
 
Set permissions on your C<.htpasswd> and log files.
 
  $ chmod 660 /full/path/to/your_data_dir/.htpasswd
  $ chmod 660 /full/path/to/your_data_dir/verotel_RUM.log
 
=cut
 
our @file_config = (    # passwd file          log file
                    "$prefix/.htpasswd", "$prefix/verotel_RUM.log",
                    #   "passwd file 2", "log file 2",
                    #   "passwd file 3", "log file 3",
                    # and so on
 
                    # or if you want to chain-call another RUM script
                    #  running on another server
                    #
                    #   "http://your.server/cgi/rum_script.pl?", "",
                    #
                    # note 'http://' at the beginning and '?' at the
                    # end of the URL are mandatory. Log file name is empty.
                   );
 
our $suffix = '.tmp';
 
=head2 $access_lock_file
 
This file is used as a lock to prevent concurrent changes to C<$storage_file>.
 
Don't forget to set the same permissions as above.
 
  $ chmod 660 /home/xxxxxxx2/data/.htlock
 
=cut
 
our $access_lock_file  = "$prefix/.htlock";
 
#------------------------------------------------------------------------------
# End of configuration
#------------------------------------------------------------------------------