Starting Templeton
To start Templeton, you should first install the
software and create your configuration file.
After installing and configuring, you may start Templeton by running the
Templeton executable at the command line.
When Templeton starts, it first loads in the default configuration files.
These include:
.templetonrc in the /etc directory (Unix)
.templetonrc in the /etc/local directory (Unix)
.templetonrc, templeton.cfg, and templeto.cfg in the directory specified by the ETC environment variable
.templetonrc, templeton.cfg, and templeto.cfg in the directory specified by the HOME environment variable
.templetonrc, templeton.cfg, and templeto.cfg in the current directory
Additional configuration files may be specified as command line parameters.
Running Templeton
When Templeton starts, it displays its banner and lists all configuration files
in the order that it loads them.
If the
This command asks where retrieved files should be placed. You may either
enter a path (i.e. D:\FILES\ or /tmp/retrieve) or the word "none". "None"
informs Templeton not to retrieve files. If you operate your own
web server, you may specify the root directory for that web server.
|
Host restriction [yes|no|host|.domain]: |
This is the first restriction option. Templeton has the ability to
retrieve from many machines, a few machines, or only one machine. Entering
"yes" tells Templeton not to leave the machine listed in the initial URL.
Entering "no" allows Templeton to retrieve from all machines that it comes
across (follow all links) -- this is dangerous since (theoretically) it can
retrieve THE ENTIRE WEB consisting of MILLIONS OF TERABYTES of data.
You may specify a specific host, such as www.intel.com. Finally, you may
specify a domain suffex. Only machines with that suffex will be retrieved.
For example, to retrieve only information from Texas A&M University, you
would enter ".tamu.edu". If you want to further restrict it to the Computer
Science department, you would use ".cs.tamu.edu".
|
Should the host's subtree be restricted [yes|no|/path]: |
When restricting to a specific host, you may also specify a restrictive
subtree on the host. Templeton will not follow links beyond the specified
subtree. Entering "yes" will restrict searches to the subtree specified in
the initial URL. For example, http://c.gp.cs.cmu.edu:5103/prog/webster
has the initial path "/prog". HTML documents not in the /prog directory
would not be retrieved. Entering "no" places no restriction on the path,
allowing Templeton to wander over the entire web site.
Alternately, you may specify a path. This is useful when the starting
URL is not the top of the directory tree. (Frequently, a web page may
not be reachable from a page "above" it. This "lower" page may still be
the "root" of the virtual subtree.)
|
Enter maximum depth [0 for unlimited]: |
This allows you to specify the number of links to follow. '1' will only
return the web page specified by the initial URL. '2' will retrieve the
initial URL and all links from that page (restrictions permitting). The larger
the number, the more levels of indirect links that will be retrieved. Entering
'0' will not restrict the number of links. If you are unsure of the number
or links you will require, you should enter a finite number, such as '3', '5',
or '10'.
|
An example response is:
Enter starting URL: http://www.cs.tamu.edu/people/
Enter local path ["none" for log files only]: /temp
Host restriction [yes|no|host|.domain]: yes
Should the host's subtree be restricted [yes|no|/path]: /people
Enter maximum depth [0 for unlimited]: 3
Files Generated
Templeton will generate a number of files. The files names use the default
sleep interval.
v or V |
View the list of URLs to process. These are listed in the order that they
will be processed, from top to botton. This list includes images, map files,
and documents. |
q or Q |
Quit Templeton |
x or X |
Exit Templeton. Currently, there is no difference between quitting
and exiting. |
any other key |
Any other key will pause the system. It is not considered "nice" to pause
the system while it is reading from the remote server since you will be
pausing a "live" network connection and taking valuable time from the
remote WWW server. "Live" connections that are paused for extended
durations will be closed by the remote server.
|
[Main Menu]
[Configuration]
[Licensing Agreement]
[Registration Information]
Document revision: 26 Oct. 1996 for Templeton 1.780 beta
Copyright 1996 N.A. Krawetz
Modification, republication, and redistribution of this
document is strictly prohibited. All rights reserved.