Note: this is a modified version of the original FAQ .
      Items which do not apply anymore have been removed, and
      information has been updated where necessary.

File:		FAQ

Date:		May 14, 1994

Last Modified:	Feb 20, 2006

Description:	Common questions and answers about jugtail.

-------------------------------------------------------------------------
Questions in this FAQ (Frequently Asked Questions) document:

Q1:  What is the difference between Jugtail and Veronica?

Q2:  What platforms can jugtail run on?

Q3:  Is jugtail freely available?

Q4:  Where can I get jugtail?

Q5:  I build the jugtail database and index tables with no problem but when I
     run jugtail as a search engine only the first level menu is available.

Q6:  After I rebuild the database and associated index and hash tables, and
     move these files into the correct location all searches I do return
     incorrect data.

Q7:  When building the jugtail database jugtail gets in a hanged state and
     does nothing.

Q8:  I have data served by my gopher server that is only relevant to the
     users in my domain and I don't want to give this database jugtail uses
     to veronica, but still want to help veronica harvest its data, how do
     I do this?

-------------------------------------------------------------------------
Q1:  What is the difference between Jugtail and Veronica?

    1.	Jugtail is built to index one gopher server, or at most a small
	cluster of servers ... this means that its response time can be
	much faster, and because its dataset is smaller, many campuses
	can afford to run a jugtail index for their local gophers.
	Veronica by contrast requires significant hardware and there are
	not many veronica servers available.  So, if you know which campus
	or institution you want to search, you should use the jugtail at
	that campus ( if it has one ) - because you will get faster
	response and leave the limited veronica search capacity for
	someone who needs a net-wide search.

   2.	Jugtail indexes are usually rebuilt daily, whereas veronica index
	is rebuilt at intervals between one week and one month, depending
	on the site ...  jugtail indexes are usually more up-to-date.
 
   3.	Both veronica and jugtail search only the titles of gopher items,
	not full text.  Some work is being done on efficient full-text
	indexing, which may blossom in improved veronicas and jugtails
	in the future.

   4.	veronica and jugtail work together with jugtail passing the
	data onto veronica when veronica is harvesting its data.  This
	allows for a rapid update of the veronica indexes.  This is
	only evident to users due to the lower ratio of extinct links
	in veronica searches.

-------------------------------------------------------------------------

Q2:  What platforms can jugtail run on?

    jugtail should be able to run on most Unix-like (POSIX) systems.
    Portability changes are very recent. Please report any problems
    you might experience on your platform.
 
-------------------------------------------------------------------------
Q3:  Is jugtail freely available?

    jugtail is
    Copyright 1993, 1994, 2006 University of Utah Computer Center

    and is available under the GNU GPL version 2 license.
    See COPYING file for the details.
    
-------------------------------------------------------------------------
Q4:  Where can I get jugtail?

    jugtail is currently available at:
    http://www.nongnu.org/jugtail

    A gopher host willing to distribute the program would be desirable.
    
-------------------------------------------------------------------------
Q5:  I build the jugtail database and index tables with no problem but when I
     run jugtail as a search engine only the first level menu is available.

   jugtail builds the database by only traversing sites you specify, and
   each site you specify must be a Fully Qualified Domain Name (FQDN).
   jugtail keeps a list of sites you want to search and does NOT map
   these machine names to an IP-Address.  Thus if your gopher server is
   running on a machine called some.machine.name and you have aliased
   gopher.machine.name to some.machine.name, jugtail does NOT recognize
   these names as the same.  To get around this problem make sure your
   gopher server is using the 'hostalias' in the gopher server
   configuration file, and specify all the names your machine is known
   by on the command line.

-------------------------------------------------------------------------
Q6:  After I rebuild the database and associated index and hash tables, and
     move these files into the correct location all searches I do return
     incorrect data.

   Once you move the data into place don't forget to send jugtail
   the SIGHUP signal.  This can be easily done with the following
   command, assuming default prefix and localstatedir (see configure --help):

	kill -HUP `/usr/bin/head -1 /usr/local/var/jugtail.pid`

   Alternativly take a look at the jugtail.sample.csh file, included
   with the distribution.  This file is a cron script which not only
   rebuild the data file and associated index and hash table, it
   also SIGHUP's jugtail or starts if from scratch if it's not running.

-------------------------------------------------------------------------
Q7:  When building the jugtail database jugtail gets in a hanged state and
     does nothing.

   This could be due to a couple of things:
   1.  You have ftp items being provided by your gopher server and
       in the ftp space there exists a recurrsive symbolic link.

       The only way around this problem is either remove the symbolic
       link causing the recurrsive loop, or use the appropriate flags
       on the command line such as
          -X "ftp:*"

   2.	The gopher server being traversed in not a daemon and started
        via inetd.  The only way around this one is to ensure the
        gopher server is running as a daemon.
        If this is the problem jugtail will timeout after 5 minutes,
        note there was a problem with the host, and continue.  jugtail
        will not attempt another connection to any host which timedout
        or could not be contacted.

-------------------------------------------------------------------------
Q8:   I have gopher data served that is only relevant to the users in
      my domain and I don't want to give this database to veronica,
      but still want to help veronica harvest its data, how does one
      go about this?

      Use the -V flag in conjunction with the -b flag.  This will build
      a data file with a ".veronica" extention which contains no items
      with "Disallow:" paths as specified in the veronica.ctl file or
      any items not provided by gopher servers you instructed jugtail
      to search.  If this ".veronica" file resides in the same location
      as your jugtail data file, simply have the veronica.ctl use:

veronica-datafile: gopher://jugtail.server.host:jugtail-port/0?datafile

       which tells veronica to get the needed database directly from
       your jugtail server "jugtail.server.host" running out port
       "jugtail-port".

    You can place any data file you wish to provide veronica in your
    gopher space.  Just make sure it is hidden, and specify the appropriate
    veronica-datafile URL in the veronica.ctl file.

-------------------------------------------------------------------------
