add release dir
This commit is contained in:
34
release/base/help/english/set/=
Normal file
34
release/base/help/english/set/=
Normal file
@@ -0,0 +1,34 @@
|
||||
|
||||
The 'set' command allows you to set one of archie's variables. Their
|
||||
values affect how archie interacts with the user. archie distinguishes
|
||||
between three types of variable: "boolean", which may be either set or
|
||||
unset, "numeric", representing an integer within a pre-determined range,
|
||||
and "string", whose value is a string of characters (which may or may
|
||||
not be restricted).
|
||||
|
||||
Currently, the variables that may be set are:
|
||||
|
||||
|
||||
autologout - numeric. Number of minutes before automatic log out
|
||||
compress - string. Compression algorithm to be used
|
||||
encode - string. Encoding algorithm to be used
|
||||
(with compress)
|
||||
language - string. Language of help facility
|
||||
mailto - string. Address that output is to be mailed to
|
||||
match_domain - string. List of domains of sites for matches
|
||||
match_path - string. List of filename components for matches
|
||||
maxhits - numeric. 'find' stops after this many hits
|
||||
maxhitspm - numeric. Max number of hits per given filename
|
||||
maxmatch - numeric. Max number of filenames to return
|
||||
max_split_size - numeric. Approx. max size of file part to be mailed
|
||||
output_format - string. How the output is to be displayed
|
||||
pager - boolean. If set, use the pager, otherwise don't
|
||||
search - string. How 'find' is to search the database
|
||||
sortby - string. How 'find' output is to be sorted
|
||||
status - boolean. Report how the search is progressing
|
||||
term - string. Describes your terminal
|
||||
|
||||
|
||||
Each variable has a corresponding subtopic entry under 'set'. See them for
|
||||
more details. Also, see help on 'unset' and 'show'.
|
||||
|
||||
14
release/base/help/english/set/autologout/=
Normal file
14
release/base/help/english/set/autologout/=
Normal file
@@ -0,0 +1,14 @@
|
||||
|
||||
By default, archie will exit after one hour of idle time. This value can be
|
||||
changed though the 'autologout' variable, which represents, in minutes, the
|
||||
length of idle time before you are logged out.
|
||||
|
||||
The minimum and maximum values are 1 and 300, representing one minute
|
||||
through five hours.
|
||||
|
||||
Example:
|
||||
|
||||
set autologout 45
|
||||
|
||||
will cause you to be automatically logged out after 45 minutes of idle time.
|
||||
|
||||
5
release/base/help/english/set/compress/=
Normal file
5
release/base/help/english/set/compress/=
Normal file
@@ -0,0 +1,5 @@
|
||||
|
||||
This variable determines the kind of data compression
|
||||
the user can specify when mailing back output.
|
||||
Currently allowed values are "none" and "compress"
|
||||
(standard UNIX compress program) with a default of "none"
|
||||
6
release/base/help/english/set/encode/=
Normal file
6
release/base/help/english/set/encode/=
Normal file
@@ -0,0 +1,6 @@
|
||||
This variable determins the type of post-compression
|
||||
encoding the user can specify when mailing back output.
|
||||
Currently allowed values are "none" and "uuencode", with
|
||||
a default of "none". Note that this variable is ignored
|
||||
unless compression is enabled (via the compress)
|
||||
variable.
|
||||
3
release/base/help/english/set/language/=
Normal file
3
release/base/help/english/set/language/=
Normal file
@@ -0,0 +1,3 @@
|
||||
This variable allows the user to specify the language in
|
||||
which the help, etc. is presented. Individual servers
|
||||
may be configured for a range of languages.
|
||||
30
release/base/help/english/set/mailto/=
Normal file
30
release/base/help/english/set/mailto/=
Normal file
@@ -0,0 +1,30 @@
|
||||
|
||||
'mailto' is a string variable whose value is a mail address (or
|
||||
comma-separated list of addresses). If this is set and the 'mail'
|
||||
command is issued with no arguments, then the output of the last command
|
||||
is mailed to that address.
|
||||
|
||||
Example:
|
||||
|
||||
set mailto user@frobozz.com
|
||||
|
||||
Example:
|
||||
|
||||
set mailto user1@hello.edu,user2@goodbye.com
|
||||
|
||||
All the various Internet addressing styles are understood. BITNET sites
|
||||
should use the convention
|
||||
|
||||
user@sitename.bitnet
|
||||
|
||||
UUCP addresses can be specified as
|
||||
|
||||
user@sitename.uucp
|
||||
|
||||
If you would like to mail to an Internet IP address then use '[]'.
|
||||
|
||||
Example:
|
||||
|
||||
set mailto bajan@[132.206.44.5]
|
||||
|
||||
|
||||
28
release/base/help/english/set/match_domain/=
Normal file
28
release/base/help/english/set/match_domain/=
Normal file
@@ -0,0 +1,28 @@
|
||||
'match_domain' is a string variable which allows you to restrict the scope
|
||||
of your search by only matching results at those sites which are in the
|
||||
pseudo-domain list you have set.
|
||||
|
||||
See help on the 'domains' command for an explanation of archie
|
||||
psuedo-domains.
|
||||
|
||||
The syntax for this command is:
|
||||
|
||||
set match_domain <pseudo-domain>[[':'<pseduo-domain>]...]
|
||||
|
||||
therefore you could say
|
||||
|
||||
set match_domain ca:mx:uk
|
||||
|
||||
which would restrict your search to sites in Canada ("ca"), Mexico
|
||||
("mx") and the United Kingdom ("uk")
|
||||
|
||||
Comparisons between the domain restrictions given and any site name are
|
||||
case insensitive and performed from right to left. Therefore the
|
||||
pseudo-domain list "EDU:va.us" will match any sites ending in "edu" or
|
||||
in "va.us" (educational US sites and some of those in Virginia).
|
||||
|
||||
DNS names to any level may be supplied. You may use any combination of
|
||||
real DNS domains and pseudo-domains to specify the restriction criteria,
|
||||
however, any pseudo-domain specified must be supported by the current
|
||||
server. See the "domains" command for a further explanation and list of
|
||||
domains supported.
|
||||
22
release/base/help/english/set/match_path/=
Normal file
22
release/base/help/english/set/match_path/=
Normal file
@@ -0,0 +1,22 @@
|
||||
The 'match_path' string variable allows you to restrict your search based
|
||||
on pathname components. For example, if you are only looking for DOS PC
|
||||
programs and think that site administrators may have put such files in
|
||||
directories with names like "PC", "DOS" or "IBM" then you could set the
|
||||
match_path variable as:
|
||||
|
||||
set match_path PC:DOS:IBM
|
||||
|
||||
All files returned must have one or more of these components in its
|
||||
pathname (the list of directories leading to the file or directory).
|
||||
|
||||
The general syntax is:
|
||||
|
||||
set match_path <component>[[':'<component>]...]
|
||||
|
||||
Note that the component names are always matched on a case-insensitive
|
||||
basis. Also, there is an implicit logical OR between components: in the
|
||||
example above the system matches it as "PC or DOS or IBM" so that if any
|
||||
one of the components match, then the condition is satisfied.
|
||||
|
||||
|
||||
|
||||
7
release/base/help/english/set/max_split_size/=
Normal file
7
release/base/help/english/set/max_split_size/=
Normal file
@@ -0,0 +1,7 @@
|
||||
This variable set the approximate maximum size, in
|
||||
bytes, of a file to be mailed to the user. Any output
|
||||
larger than this limit will be split in pieces of about
|
||||
this size. This can be set by the user in the range 1024
|
||||
to ~2Gb with a default of 51200 bytes. Some mail
|
||||
gateways will not allow results of over 100Kb and so
|
||||
care should be taken when setting this limit.
|
||||
55
release/base/help/english/set/maxhits/=
Normal file
55
release/base/help/english/set/maxhits/=
Normal file
@@ -0,0 +1,55 @@
|
||||
|
||||
You can control the number of results returned in the archie system by 3
|
||||
variables. 'maxhits', 'maxmatch' and 'maxhitspm'.
|
||||
|
||||
'maxhits' is a numeric variable whose value is the maximum number of
|
||||
matches you want the 'find' command to generate.
|
||||
|
||||
If archie seems to be slow, or you don't want a lot of output this can be
|
||||
set to a small value. "maxhits" must be within the range 0 to 1000. The
|
||||
default value is 1000.
|
||||
|
||||
Example:
|
||||
|
||||
set maxhits 100
|
||||
|
||||
'find' will now stop after 100 matches have been found
|
||||
|
||||
There are 2 variables which work with the 'maxhits' variable to modify
|
||||
the behavior of the search mechanism. They are 'maxmatch' and
|
||||
'maxhitspm'. The database can be viewed as follows:
|
||||
|
||||
|
||||
filename1 ----> file1 -> file2 -> file3
|
||||
|
|
||||
V
|
||||
filename2 ----> file1 -> file2 -> file3 -> file4
|
||||
|
|
||||
V
|
||||
filename3 ----> file1
|
||||
|
|
||||
V
|
||||
(etc)
|
||||
|
||||
Each filename can have several files associated with it which share that
|
||||
name. For example, the string "README" is only stored once but points to
|
||||
the information for each of the files in the database called README
|
||||
spread around all the anonymous FTP sites on the Internet (which, as you
|
||||
can imagine are numerous).
|
||||
|
||||
The maximum total number of "files" (hits) returned is determined by the
|
||||
'maxhits' variable. The maximum number of filenames that match is
|
||||
determined by the 'maxmatch' variable. Finally if you only want to
|
||||
return a limited number of files for each filename matched, use the
|
||||
'maxhitspm' variable.
|
||||
|
||||
If you do the following:
|
||||
|
||||
set maxhits 20
|
||||
set maxmatch 5
|
||||
set maxthitspm 7
|
||||
|
||||
Then you will match at most 5 filenames. For each filename you will be
|
||||
given back at most 7 files with that name. However, in total you will
|
||||
only be returned 20 hits, since maxhits operates on the total number
|
||||
regardless of the the combinations of the hits.
|
||||
55
release/base/help/english/set/maxhitspm/=
Normal file
55
release/base/help/english/set/maxhitspm/=
Normal file
@@ -0,0 +1,55 @@
|
||||
|
||||
You can control the number of results returned in the archie system by 3
|
||||
variables. 'maxhits', 'maxmatch' and 'maxhitspm'.
|
||||
|
||||
'maxhits' is a numeric variable whose value is the maximum number of
|
||||
matches you want the 'find' command to generate.
|
||||
|
||||
If archie seems to be slow, or you don't want a lot of output this can be
|
||||
set to a small value. "maxhits" must be within the range 0 to 1000. The
|
||||
default value is 1000.
|
||||
|
||||
Example:
|
||||
|
||||
set maxhits 100
|
||||
|
||||
'find' will now stop after 100 matches have been found
|
||||
|
||||
There are 2 variables which work with the 'maxhits' variable to modify
|
||||
the behavior of the search mechanism. They are 'maxmatch' and
|
||||
'maxhitspm'. The database can be viewed as follows:
|
||||
|
||||
|
||||
filename1 ----> file1 -> file2 -> file3
|
||||
|
|
||||
V
|
||||
filename2 ----> file1 -> file2 -> file3 -> file4
|
||||
|
|
||||
V
|
||||
filename3 ----> file1
|
||||
|
|
||||
V
|
||||
(etc)
|
||||
|
||||
Each filename can have several files associated with it which share that
|
||||
name. For example, the string "README" is only stored once but points to
|
||||
the information for each of the files in the database called README
|
||||
spread around all the anonymous FTP sites on the Internet (which, as you
|
||||
can imagine are numerous).
|
||||
|
||||
The maximum total number of "files" (hits) returned is determined by the
|
||||
'maxhits' variable. The maximum number of filenames that match is
|
||||
determined by the 'maxmatch' variable. Finally if you only want to
|
||||
return a limited number of files for each filename matched, use the
|
||||
'maxhitspm' variable.
|
||||
|
||||
If you do the following:
|
||||
|
||||
set maxhits 20
|
||||
set maxmatch 5
|
||||
set maxthitspm 7
|
||||
|
||||
Then you will match at most 5 filenames. For each filename you will be
|
||||
given back at most 7 files with that name. However, in total you will
|
||||
only be returned 20 hits, since maxhits operates on the total number
|
||||
regardless of the the combinations of the hits.
|
||||
55
release/base/help/english/set/maxmatch/=
Normal file
55
release/base/help/english/set/maxmatch/=
Normal file
@@ -0,0 +1,55 @@
|
||||
|
||||
You can control the number of results returned in the archie system by 3
|
||||
variables. 'maxhits', 'maxmatch' and 'maxhitspm'.
|
||||
|
||||
'maxhits' is a numeric variable whose value is the maximum number of
|
||||
matches you want the 'find' command to generate.
|
||||
|
||||
If archie seems to be slow, or you don't want a lot of output this can be
|
||||
set to a small value. "maxhits" must be within the range 0 to 1000. The
|
||||
default value is 1000.
|
||||
|
||||
Example:
|
||||
|
||||
set maxhits 100
|
||||
|
||||
'find' will now stop after 100 matches have been found
|
||||
|
||||
There are 2 variables which work with the 'maxhits' variable to modify
|
||||
the behavior of the search mechanism. They are 'maxmatch' and
|
||||
'maxhitspm'. The database can be viewed as follows:
|
||||
|
||||
|
||||
filename1 ----> file1 -> file2 -> file3
|
||||
|
|
||||
V
|
||||
filename2 ----> file1 -> file2 -> file3 -> file4
|
||||
|
|
||||
V
|
||||
filename3 ----> file1
|
||||
|
|
||||
V
|
||||
(etc)
|
||||
|
||||
Each filename can have several files associated with it which share that
|
||||
name. For example, the string "README" is only stored once but points to
|
||||
the information for each of the files in the database called README
|
||||
spread around all the anonymous FTP sites on the Internet (which, as you
|
||||
can imagine are numerous).
|
||||
|
||||
The maximum total number of "files" (hits) returned is determined by the
|
||||
'maxhits' variable. The maximum number of filenames that match is
|
||||
determined by the 'maxmatch' variable. Finally if you only want to
|
||||
return a limited number of files for each filename matched, use the
|
||||
'maxhitspm' variable.
|
||||
|
||||
If you do the following:
|
||||
|
||||
set maxhits 20
|
||||
set maxmatch 5
|
||||
set maxthitspm 7
|
||||
|
||||
Then you will match at most 5 filenames. For each filename you will be
|
||||
given back at most 7 files with that name. However, in total you will
|
||||
only be returned 20 hits, since maxhits operates on the total number
|
||||
regardless of the the combinations of the hits.
|
||||
4
release/base/help/english/set/output_format/=
Normal file
4
release/base/help/english/set/output_format/=
Normal file
@@ -0,0 +1,4 @@
|
||||
Affects the way the output of "find" and "list" is
|
||||
displayed. User settable, with valid values of "machine"
|
||||
(machine readable format), "terse" and "verbose", with a
|
||||
default of "verbose".
|
||||
11
release/base/help/english/set/pager/=
Normal file
11
release/base/help/english/set/pager/=
Normal file
@@ -0,0 +1,11 @@
|
||||
|
||||
'pager' is a boolean variable which, when set, tells archie to filter all
|
||||
output through the pager "less".
|
||||
|
||||
It improves the look of the output (but is not necessary) if you also set
|
||||
the 'term' variable to your terminal type.
|
||||
|
||||
Example:
|
||||
|
||||
set pager
|
||||
|
||||
138
release/base/help/english/set/search/=
Normal file
138
release/base/help/english/set/search/=
Normal file
@@ -0,0 +1,138 @@
|
||||
|
||||
The 'search' variable determines the kind of search performed on the
|
||||
database by the 'prog' command, providing flexibilty on search times and
|
||||
ranges.
|
||||
|
||||
'search' is a string variable whose value is one of the following:
|
||||
|
||||
(1) "sub"
|
||||
|
||||
Substring (case insensitive). A simple, everyday substring search. A
|
||||
match occurs if the the file (or directory) name in the database
|
||||
contains the user-given substring.
|
||||
|
||||
Example:
|
||||
|
||||
"is" will match "islington" and "this" and "poison"
|
||||
|
||||
(2) "subcase"
|
||||
|
||||
Substring (case sensitive). As above but the case of the
|
||||
strings involved becomes significant.
|
||||
|
||||
Example:
|
||||
|
||||
"TeX" will match "LaTeX" but not "Latex" or "TExTroff".
|
||||
|
||||
|
||||
(3) "exact"
|
||||
|
||||
Exact match. The fastest search method of all. The restriction is
|
||||
that the user string (the argument to the 'prog' command) has to
|
||||
_exactly_ match (including case) the string in the database. This is
|
||||
provided for those of who who know just what you are looking for.
|
||||
|
||||
For example, if you wanted to know where all the "xlock.tar.Z" files
|
||||
were, this is the kind of search to use.
|
||||
|
||||
(4) "regex" This is the DEFAULT search method.
|
||||
|
||||
ed(1) regular expressions. Searches the database with the user
|
||||
(search) string which is given in the form of an ed(1) regular
|
||||
expression.
|
||||
|
||||
NOTE: Unless specifically anchored to the beginning (with ^) or end
|
||||
(with $) of a line, ed(1) regular expressions have ".*" prepended and
|
||||
appended to them. For example, it is NOT NECESSARY to say
|
||||
|
||||
prog .*xnlock.*
|
||||
|
||||
since
|
||||
prog xnlock
|
||||
|
||||
will suffice. Thus the regex match becomes a simple substring match.
|
||||
|
||||
There are also compound searches made up of combinations
|
||||
of the above search methods in sequence:
|
||||
|
||||
exact_sub Try "exact". If no matches found use
|
||||
"sub".
|
||||
exact_subcase Try "exact". If no matches found use
|
||||
"subcase"
|
||||
exact_regex Try "exact". If no matches found use
|
||||
regex.
|
||||
|
||||
|
||||
An "ed(1) regular expression" (from here on called RE) is the particular
|
||||
type of regular expression used in the "ed" editor under Unix. For those
|
||||
who are interested in all the gory details of REs see the help for
|
||||
"regex" (which is incomplete, at the moment :-(), otherwise what follows
|
||||
should be sufficient for most needs.
|
||||
|
||||
A regular expression is a convenient way to search for a set of specific
|
||||
strings matching a pattern. To be able to specify such a pattern with
|
||||
only the ordinary set of printable character we have to co-opt some of
|
||||
them. For example in a RE the period means _any_ single character,
|
||||
while an asterisk, '*', means zero or more occurences of the *PRECEDING*
|
||||
RE.
|
||||
|
||||
For example:
|
||||
|
||||
knob - matches any string containing the substring 'knob'
|
||||
|
||||
a*splat - matches strings that contain zero or more a's followed by the
|
||||
string 'splat'
|
||||
|
||||
#.*# - would match anything containing a '#' followed by zero or more
|
||||
occurences of _any_ character, followed by another '#'
|
||||
|
||||
Other special characters that may be useful are '[' and ']', which are
|
||||
used together. They can be used to specify either a set of characters
|
||||
to match or a set of characters to not match. An example of the first
|
||||
case is:
|
||||
|
||||
[abcd]
|
||||
|
||||
which matches any of one of the four letters, while an example of the
|
||||
second case is:
|
||||
|
||||
[^abcd]
|
||||
|
||||
in which the '^' _in_the_first_position_ means that any character _not_
|
||||
in the list will be matched. As well, ranges can be specified with a
|
||||
'-'.
|
||||
|
||||
[a-z]
|
||||
|
||||
matches any lower case letter and,
|
||||
|
||||
[^a-z]
|
||||
|
||||
matches any character other than a lower case letter. Furthermore, you
|
||||
can specify multiple ranges such as:
|
||||
|
||||
[%@a-z0-9]
|
||||
|
||||
or
|
||||
|
||||
[^A-Za-z]
|
||||
|
||||
meaning: match '%' or '@' or any lower case letter or digit, and match
|
||||
any character other than a letter, respectively.
|
||||
|
||||
When you want to match a character which has a special meaning you should
|
||||
precede it by a backslash, '\'.
|
||||
|
||||
Some final examples of REs are:
|
||||
|
||||
[Mm]ac\.txt - match anything containg the string "Mac.txt" or
|
||||
"mac.txt"
|
||||
|
||||
[^aeiou][^aeiou]* - match any string consisting entirely of non-vowels
|
||||
|
||||
foo-v[0-9]\.tar\.Z - match "foo-v0.tar.Z" through "foo-v9.tar.Z"
|
||||
|
||||
|
||||
Good luck, and remember that many things can be found with only a simple
|
||||
substring (e.g. latex).
|
||||
|
||||
4
release/base/help/english/set/server/=
Normal file
4
release/base/help/english/set/server/=
Normal file
@@ -0,0 +1,4 @@
|
||||
This variable determines archie/Prospero server to which
|
||||
the email interface connects when "find" or "list"
|
||||
commands are used. Usually defaults to "localhost" on
|
||||
most archie systems.
|
||||
49
release/base/help/english/set/sortby/=
Normal file
49
release/base/help/english/set/sortby/=
Normal file
@@ -0,0 +1,49 @@
|
||||
|
||||
The 'sortby' variable describes how the output from the 'prog' command
|
||||
is to be ordered. It can have one of 5 values (and their associated
|
||||
reverse orders). For each method, the "natural" sort order (or at least,
|
||||
what we consider to be the natural order) is the default.
|
||||
|
||||
The reverse sorting orders from those described here are obtained by
|
||||
prepending "r" to the 'sortby' value given. (Eg. reverse hostname order
|
||||
"hostname" is "rhostname").
|
||||
|
||||
|
||||
(1) "hostname"
|
||||
|
||||
Output is sorted on the archive hostname in lexical order.
|
||||
|
||||
Reverse order "rhostname".
|
||||
|
||||
(2) "time"
|
||||
|
||||
Output is sorted with the most recent modifcation times of the found
|
||||
file/directory names coming first (youngest -> oldest).
|
||||
|
||||
Reverse order "rtime".
|
||||
|
||||
(3) "size"
|
||||
|
||||
Output is sorted by the size of the found files/directories, largest
|
||||
first.
|
||||
|
||||
Reverse order "rsize".
|
||||
|
||||
(4) "filename"
|
||||
|
||||
Sorted in file/directory name lexical order.
|
||||
|
||||
Reverse order "rfilename".
|
||||
|
||||
(5) "none" This is the DEFAULT order.
|
||||
|
||||
Unsorted. There is no reverse order although "rnone" is accepted for
|
||||
symmetry.
|
||||
|
||||
|
||||
Typing the keyboard interrupt character ( Ctl-C for most people on UNIX)
|
||||
during a search will cause the search to aborted. The results up to that
|
||||
time will be sorted (determined by the value of the sortby variable) and
|
||||
the results output. This output phase may be aborted by typing the abort
|
||||
character a second time.
|
||||
|
||||
22
release/base/help/english/set/status/=
Normal file
22
release/base/help/english/set/status/=
Normal file
@@ -0,0 +1,22 @@
|
||||
The 'status' variable is a boolean value:
|
||||
|
||||
set status
|
||||
|
||||
turns it on and
|
||||
|
||||
unset status
|
||||
|
||||
turns it off. When set in interactive mode, it will display the queue
|
||||
position of your request and the estimated time for completion of the
|
||||
request in minutes and seconds.
|
||||
|
||||
The estimated time is an average of the time taken for the previous 10
|
||||
similar requests completed by the current server. The queue position is
|
||||
determined by the type of request. For example, "exact" matches have
|
||||
priorities over all other match types since they are the fasted to
|
||||
complete.
|
||||
|
||||
The variable also turns on a moving 'marker' which indicates that the
|
||||
system is processing your request.
|
||||
|
||||
Setting this variable has no effect in the email interface.
|
||||
22
release/base/help/english/set/term/=
Normal file
22
release/base/help/english/set/term/=
Normal file
@@ -0,0 +1,22 @@
|
||||
|
||||
The 'term' variable tells archie what type of terminal you are using, and
|
||||
optionally its size in rows and columns. This information is used by the
|
||||
pager.
|
||||
|
||||
The usage is:
|
||||
|
||||
set term <terminal-type> [<#rows> [<#columns>]]
|
||||
|
||||
That is, the terminal type is required, but the number of rows and
|
||||
columns is optional. You may specify a value for rows only, but if you
|
||||
want to change the number of columns you must give a value for _both_
|
||||
rows and columns. The default values for rows and columns are 24 and 80.
|
||||
|
||||
Examples:
|
||||
|
||||
set term vt100
|
||||
|
||||
set term xterm 60
|
||||
|
||||
set term xterm 24 100
|
||||
|
||||
Reference in New Issue
Block a user