
Q: How can I start the index process?
A: 1. verify cgi-bin/ftplocate/config
      to see if the default value fits your server configuration.
      The $CACHEDIR $USERLOG $TMPDIR must be owned by the same user 
      as your web server runs with.
   2. edit cgi-bin/ftplocate/config.site
      to list all the ftp server you want to index 
   3. execute the cgi-bin/ftplocate/indexer.sh

Q: The indexer.sh could not work?
   The error message is 
   "Can't locate asm/unistd.ph in @INC (did you run h2ph?)..."
A: Please execute the following command with root

   cd /usr/include
   h2ph -r -l .

   (Don't forget the lat dot '.', which represents the current directory)

Q: The indexer.sh could not work?
   The error message is "Command not found"
A: Please check the location of your perl interpreter.
   And change the #!/usr/bin/perl in the following scripts to that location

   dcollect.pl
   dindex.pl
   dsearch.pl
   flcatsite.pl
   flcollect.pl
   flfilter.pl
   flhistory.pl
   flindex.pl
   flmap.pl
   flsearch.pl
   flserv.pl
   flsummary.pl
   fltop.pl
   fltrain.pl

Q: The perl path is correct, but the error "Command not found" still appears?
A: Please check the cgi-bin/ftplocate/config to see
   if all defined commands CMD_* are available in your system.

Q: What is the startup URL of the ftplocate search engine?
A: It should be http://yourserver/cgi-bin/flsearch.pl in normal case.

Q: The indexer.sh completed without any problem,
   but I got no output in the ftp search?
A: Please be sure the $CACHEDIR, $TMPDIR, $USERLOG and $MAPLOG is owned 
   by the effective user of your web server process
   If you don't know what is the effective user of your web server process,
   you may try to set the mod 777 for directory $CACHEDIR and $TMPDIR
   