MAN page from Other autorpm-1.9.7-1.noarch.rpm

AUTORPM.CONF

Section: User Manuals (5)
Updated: MARCH 1998
Index

NAME

autorpm.conf - Config file for AutoRPM

SYNOPSIS

autorpm.conf

DESCRIPTION

Theautorpm.conf file is the config file for AutoRPM. It is usually locatedin /etc/autorpm.d, but it can be placed anywhere if the --config command lineoption is given to AutoRPM.

FILE FORMAT

The file looks much like standard C or Perl. Commands can be the form:

Command_Name (Argument);

notice the semicolon at the end and the parenthesis around the argument. Blocks can be of the form:

Block_Name (Argument) {

Another_Command (Argument);

}

The parsing is very forgiving as to where you place the curly-braces.The important thing to note is that the Block contains Commands insideof it.

Comments begin with the # character and continue to the end of the line.Comments can be on a line by themselves or can follow a command.

As I said, the parsing is very forgiving. Commands can even be split intoseveral lines. The following is identical to the Command_Name example above(although harder to read):

Command_Name #bla bla

( #more stuff

# and more

Argument # and more

) # and more

; # and more

The only thing that cannot be split up between lines is an argument that is a string.See the section below on arguments.

Everything is caseinsensitiveunless it is enclosed in quotes. See the next section on arguments.

ARGUMENTS

Most arguments are either a string or a Yes/No. Strings must have aopening double-quote (") and a closing double-quote on the same line.Anything may be placed inside of a string, even including unescaped double-quotes.

Anything inside of quotes is treated as casesensitive, so make sure the case is correct inside of strings.

MAIN FILE & BLOCKS

All commands may be in either the main file or in a block. It is avery good idea to put all Main-File commandsbeforeany Source-Blocks.

Main-Filecommands are simply commands that do not belong insideany blocks (Temp_Dir is an example of this).

There are 2 kinds of blocks: Source-Blocks and Action-Blocks.

Source-Blocksdirect AutoRPM towards a particular source of RPMs. Inside the Source-Blockis a series of Commands and/or Action-Blocks. Anything inside of a Source-Blockapplies only to that particular source of RPMs. Source blocks may not be nested (in other words, they are only allowed to appear in the Main File).

Action-Blocksdefine a set of commands to perform when new or updated RPMs are foundin the current source of RPMs. Action-Blocks are only valid inside ofSource-Blocks.

REPEATED COMMANDS

Many commands can be repeated as many times as you need. This means that youcan do something like the following:

Regex_Ignore ("^kernel");

Regex_Ignore ("^pcmcia-cs");

Regex_Ignore ("^X");

to ignore all RPMs that begin with kernel or pcmcia-cs or X.

ACCEPT & IGNORE COMMANDS & REGULAR EXPRESSIONS

First of all, all the Accept/Ignore commands (except Accept/Ignore Arch) take a regular expression as its argument. All regular expressions should be enclosedin quotes, not slashes. Other than that, the regular expressions are standard Perl.As an example, this Regex in Perl would match anything that begins with the letter 'a':

/^a/

If you wanted to accept only RPMs that begin with a lowercase 'a', you would do:

Regex_Accept ("^a");

The following rules apply to all groups of Accept/Ignore commands:

1)

If neither an Accept nor Ignore are given, all will be Accepted.

2)

If only one or more Ignores are given, RPMs will be Ignored if they matchthe Ignored values, but Accepted otherwise.

3)

If only one or more Accepts are given, RPMs willonlybe Accepted if they match oneof the Accepted values.

4)

If both Accepts and Ignores are given, RPMs will always be Ignored if theymatch an Ignore, and will only be Accepted if they match an accept. If an RPMmatches both an Accept and an Ignore, it will be Ignored.

MAIN-FILE COMMAND SUMMARY

These commands are only valid inside of the Main-File. These commands should beplacedbeforeany Source-Blocks.

Command:

Config_Dir ("directory");

Can Be Repeated:

Yes

Default:

none

Description:

You can specify a directory (i.e. /etc/autorpm.d). Thisdirectory can have several files that are basically "appended"to the end of the main configuration file at runtime. Thisallows a person to create a specific file in that directoryfor every "logical group". For example, there could be a official updates for RHL6.0, and an 'autorpm' file that checkedfor updates for autorpm, etc. These files are the exact sameformat as the main file (/etc/autorpm.d/autorpm.conf).

Command:

Config_File ("directory");

Can Be Repeated:

Yes

Default:

none

Description:

You can specify specific files to "insert" into the main configfile. The above Config_Dir() command inserts all the files ina certain directory... this only inserts a specific file.All of the commands in the main config file are run first. Then,all of the Config_File() commands are run in the same order as theyappear in the file. Finally, all of the Config_Dir()'s are processed.

Command:

Set_Var ("name", "value");

Description:

You can set an environment variable in this way. The name andvalue both retain their case if enclosed in quotes as shown above.The variable can then be used as part of (or the entire) parameterfor a later command. The variable is accessed like this (basically,${VarName}):

Set_Var ("Test", "Hello");

SomeOtherCommand ("hello - ${Test}");

Command:

Read_Var ("name", "file");

Description:

You can set an environment variable in this way. The value of thevariable is the first line of the specified file. The variable canthen be used as part of (or the entire) parameter for a later commandas illustrated above.

Command:

Eval_Var ("name", "command");

Description:

You can set an environment variable in this way. The value of thevariable is the output after running the specified command. The variablecan then be used as part of (or the entire) parameter for a later commandas illustrated above.

Command:

Report_Queues_To ("email_address");

Can Be Repeated:

Default:

"PRINT" (special string to print report to the screen)

Description:

This is the email address to mail the Queue report to. The Queuereport includes the installation process of RPMs in the Auto-Queueas well as a notification of the number of RPMs in the InteractiveQueue. This report will *only* be sent if an RPM is installed *or*there is at least one RPM in the Interactive queue. There is onespecial email address, "PRINT" (must be in all caps with quotes aroundit) that will actually display the report to the screen. If thegiven argument is null (Report_Queues_To ("");), no report will begenerated.

Command:

FTP_Retries ("number_of_tries");

Can Be Repeated:

Default:

2 tries

Description:

This is the number of attempts AutoRPM will make at connecting toan FTP site before giving up.

Command:

Replace_Arch ("old_arch", "new_arch");

Can Be Repeated:

Yes

Default:

N/A

Description:

By default, AutoRPM will only match local RPMs that have the samearchitecture as the remote RPM specifies in its filename (the exceptionis if the remote RPM is `noarch', then any local architecture will match).However, some Linux distributions (namely Mandrake) name their RPMsthey are installed. This will confuse AutoRPM, as it thinks the remoteRPM is for i586 and the local package is for i386 and it won't compare them.The truth is, if you have a i586 processor, it's okay to replace a locali386 package with a i586 package. This command will allow you to tellAutoRPM this is true. You use it like this:

Replace_Arch (i386, i586);

which means that it's okay to upgrade i386 packages with i586 packages.

Command:

FTP_Retry_Delay ("min", "max");

Can Be Repeated:

Default:

5 seconds to 600 seconds

Description:

This is the minimum and maximum number of seconds AutoRPM willwait between retries. AutoRPM will pick a random number ofseconds between the set minimum and maximum waits.

Command:

Temp_Dir ("path_name");

Can Be Repeated:

Default:

/var/spool/autorpm

Description:

This sets the directory that RPMs will temporarily be kept when they areabout to be installed or upgraded. Various small temp files are also kepthere, in addition to the Queue files and the Auto-Ignore list. NOTE: Thisshouldnotbe /tmp, /var/tmp, or any other directory that is publicly writeable, as thiscould cause some security problems.

Command:

Pool_Dir ("path_name");

Can Be Repeated:

Default:

/etc/autorpm.d/pools

Description:

This is the directory where the FTP Pool definitions reside.

Command:

RPM_Location ("path_name");

Can Be Repeated:

Default:

/bin/rpm

Description:

This is the location of your RPM binary. If you need to specify any additional

Command:

FTP_Firewall ("firewall_machine_hostname");

Can Be Repeated:

Default:

(none)

Description:

If you need to go through a firewall machine to use FTP, use this commandto set the hostname of the firewall.

Command:

FTP_Port ("remote_port");

Can Be Repeated:

Default:

Description:

This is the port to connect to on the remote machine (either the FTP siteor the firewall machine).

Command:

FTP_Passive (Yes or No);

Can Be Repeated:

Default:

Description:

Use FTP_Passive (Yes); to tell AutoRPM to use passive mode for all FTPtransfers.

Command:

FTP_TimeOut (timeout_in_seconds);

Can Be Repeated:

Default:

120 seconds

Description:

The timeout for FTP connections, in seconds.

Command:

Debug (Yes or No);

Can Be Repeated:

Default:

Description:

Turns Debug mode on or off. You may want to use this before you send me a bugreport to getmuchmore detail!

Command:

Hostname ("hostname");

Can Be Repeated:

Default:

output of the `hostname` command

Description:

If your `hostname` command doesn't return a full hostname, you should setthis to the full hostname you want to use (i.e. here.com). This will beused in the Report headers as well as part of the anonymous FTP password.

Command:

Umask ("new_umask");

Can Be Repeated:

Default:

"0007"

Description:

If you don't like the default umask that AutoRPM uses, you can changeit here... new_umask is the new octal umask.

Command:

ftp ("ftp_site_descriptor");

Special:

Begins a Source-Block

Can Be Repeated:

Yes

Default:

N/A

Description:

This starts a Source-Block. A Source-Block defines a source of RPMs to check(an FTP site in this case). The argument, ftp_site_descriptor, needs to describean FTP site as well as a directory on that FTP site. It should be in the form"ftp://ftp.somewhere.com/pub/redhat/RPMS/i386", but the older form of "ftp.somewhere.com:/pub/redhat/RPMS/i386" will still work as well. If you wantto do non-anonymous FTP logins, you may use the form"ftp://user:password@ftp.somewhere.com/pub/redhat/RPMS/i386".

Command:

ftppool ("ftp_pool_name");

Special:

Begins a Source-Block

Can Be Repeated:

Yes

Default:

N/A

Description:

This starts a Source-Block. A Source-Block defines a source of RPMs to check(a pool of FTP sites in this case). The argument, ftp_pool_name, needs tobe an existing pool of FTP sites. FTP Pools are described in more detaillater in this man page. Search for FTP POOLS.

Command:

Directory ("path_name");

Special:

Begins a Source-Block

Can Be Repeated:

Yes

Default:

N/A

Description:

This starts a Source-Block. A Source-Block defines a source of RPMs to check(a local (or NFS mounted) directory in this case).

SOURCE-BLOCK COMMAND SUMMARY

These commands are only valid inside of a Source-Block. A Source-Block beginswith either the 'ftp', 'ftppool', or 'directory' command described in the previous section.

Command:

Report_To ("email_address");

Can Be Repeated:

Default:

"PRINT" (special string to print report to the screen)

Description:

This is the email address to which to mail the report for the currentSource-Block. The contents of the report, and whether or not it willbe sent, is determined by the next command, Report_All. There is onespecial email address, "PRINT" (must be in all caps with quotes aroundit) that will actually display the report to the screen. If you have10 source blocks with 10 Report_To commands that all give the sameemail address, that person will only get one email every time AutoRPMis run. If the given argument is null (Report_To ("");), noreport will be generated.

Command:

Report_All (Yes or No);

Can Be Repeated:

Default:

Description:

The default value of No means that a report for a given Source-Blockwill only be given if some kind of action takes place. If set toYes, a report will be sent regardless of what happens. This onlyaffects reports that are sent to an email address... everything isalways reported when the report is going to the screen.

Command:

Display_Report (Yes or No);

Can Be Repeated:

Default:

Yes

Description:

Set to Yes to display the report to the screen (i.e. STDOUT). Remember, if thisruns from Cron, STDOUT usually gets mailed to root. NOTE: If all of your Action-Blocksuse Report (No);, you won't get a very detailed report anyways.

Command:

Mail_Report ("email_address");

Can Be Repeated:

Default:

(don't mail to anybody)

Description:

NOTE: This overrides Display_Report above. The report for only this particularSource-Block will be mailed to "email_address", where "email_address" is eithera local account or a full email address. The only problem with this command is,if you use it in 10 different Source-Blocks, you get 10 different emails...

Command:

Compare_To_Dir ("path_name");

Can Be Repeated:

Yes

Default:

(compare to installed RPMs)

Description:

NOTE: By specifying at least one Compare_To_Dir, the installed RPMs will nolonger be considered when looking for new or updated RPMs. You can forceAutoRPM to compare to both local files and locally installed RPMs using theCompare_To_Installed command given next. If this commandis given more than once, the files in all the directories are compared againstthe remote files. This can be quite useful for keeping a local mirror ofRPMs on an FTP site. NOTE: any subdirectories of this directory are ignored,see the section on RECURSION COMMANDS below.

Command:

Compare_To_Installed (Yes or No);

Can Be Repeated:

Default:

No if a Compare_To_Dir is given, otherwise Yes.

Description:

You really only need to use this command if you have given a Compare_To_Dircommand and you also want to compare to the locally installed RPMs. Settingthis to yes will make AutoRPM compare the remote files to the locally installedRPMs (in addition to any local files given by Compare_To_Dir commands).

Commands:

Regex_Ignore ("regex");

Regex_Accept ("regex");

Can Be Repeated:

Yes

Default:

(accept all)

Description:

These commands tell which RPM filenames to accept. See the section onACCEPT & IGNORE & REGULAR EXPRESSIONS above.

Commands:

Ignore_Arch ("regex");

Accept_Arch ("regex");

Can Be Repeated:

Yes

Default:

(accept all)

Description:

These commands tell which architectures to accept. See the section onACCEPT & IGNORE & REGULAR EXPRESSIONS above.

Command:

Action (action_type);

Special:

Begins an Action-Block

Can Be Repeated:

Yes

Default:

N/A

Description:

This starts an Action-Block. An Action-Block defines what is to be done withanyaction_typeRPMs found in the current source (FTP or directory). Note thataction_typeis not enclosed in quotes.action_type may be new or updated (or same or old if you can think of anything to dowith them).

ACTION-BLOCK COMMAND SUMMARY

These commands are only valid inside of an Action-Block. An Action-Block beginswith the 'action' command described in the previous section. If the action blockis defined with a type of 'new', then any commands inside of it will be appliedtoonly newRPMs foundonly in that source!

Command:

Store ("path_name");

Can Be Repeated:

Yes

Default:

(don't store)

Description:

Causes whatever source file is new or updated (depending on which action blockthis command is in) to be stored in the given directory. Very useful for mirroring ;).If you are also going to possibly Install this RPM, be sure to give the 'Store'command before the 'Install' command so the RPM won't be transfered twice.

Command:

Report (Yes or No);

Can Be Repeated:

Default:

Yes

Description:

This tells AutoRPM whether or not to report on RPMs that are handled bythis action block.

Command:

Report_Always (Yes or No);

Can Be Repeated:

Default:

Description:

This command will make AutoRPM always report on every RPM in this sourceblock (unless they are exactly the same as what you are locally comparingto). If you just want to see what RPMs in the directory or FTP site would orcould be installed, this will do this for you. The normal Report commandabove controls what reporting will be done on actual actions that are done.This Report command will report even if no action is done (i.e. even if itis the only command in the action block). If you put in this command aswell as other commands like "Store" or "Install", then you will get doublereporting, which is probably not what you want.

Command:

Install (Auto or Interactive or No);

Can Be Repeated:

Default:

Description:

Causes whichever RPM that is new or updated to be installed interactively orautomatically. Notice there are no quotes around the parameter. Setting thisto Auto will cause the RPM to be added to the Auto-Queue that will be executedafter all the Source-Blocks in the config file have been completed. If anyRPMs fail to install in Auto-Install-Mode, they will be placed into theInteractive-Queue. For more information on the Interactive-Queue, seeautorpm(8). NOTE: No FTP source RPMs are actually transmitted until they need to be...

Command:

RPM_Opt ("opt_string");

Can Be Repeated:

Default:

null string

Description:

If this command exists in an action block, then any RPMs in that blockwill use the given option to RPM when/if installed (automatically orinteractively).

Command:

Delete_Old_Version (Yes or No);

Can Be Repeated:

Default:

Description:

This only makes sense if a local directory is being compared against (as opposed tothe locally installed RPMs). If a local RPM is older than a Source RPM, the localRPM will be deleted. Very useful for mirroring.

Command:

Copy_After_Install ("path_name");

Can Be Repeated:

Yes

Default:

Description:

Command:

Delete_After_Install (Yes or No);

Can Be Repeated:

Default:

No (Yes for FTP sources)

Description:

The file will be deleted after a successful installation. In the case of an FTP source of RPMs, this determines whetheror not the local copy of the FTP file will be deleted (whichis usually what you want).

Command:

PGP_Require (Yes or No);

Can Be Repeated:

Default:

Description:

Although you can always manually check PGP signatures from inside Interactive-Mode,this will force the RPM to have to pass a PGP check before installing. The way thisworks isbeforethe RPM is placed into the Auto or Interactive Queue, the signature is checked againstyour public key ring. If the check fails, the default action is to place the RPM intothe Auto-Queue instead of whichever queue it was supposed to go into. You can controlwhat happens after a failed PGP check with the next command, PGP_Fail_Install.Remember, you can use the RPM_Location command to specify a 'rcfile'. Inside of thatrcfile (or in the default rcfile, /etc/rpmrc), you can specify the path to your PGPrings.

Command:

PGP_Fail_Install (Auto or Interactive or No);

Can Be Repeated:

Default:

Interactive

Description:

If the PGP check fails (only an issue if the PGP_Require command is given for thesame action block), this is what the Install command will be overridden to. So,if an action block contains Install (Auto); , PGP_Require (""); , and PGP_Fail_Install (No); ,then here is what would happen. If an RPM passed the PGP signature check (i.e. it matchesone of the public keys on the ring) it will be Auto-Installed as the Install command saysto. If the check fails, the RPM will not be installed at all (although you will stillbe notified of the failure). If, in this example, the PGP_Fail_Install command was removed,it would revert to the default of Interactive, so that if an RPM fails its PGP check, itwill be placed into the Interactive-Queue.

Command:

Ignore_On_Failure (Yes or No);

Can Be Repeated:

Default:

Description:

If set, RPMs that fail to be installed (due to errors) will be reportedonce and then will be put into the auto-ignore file. They will never gointo the Interactive queue.

RECURSION COMMANDS

These commands allow you to recursively move through the source directory orFTP site. The first command, Recursive (Yes);, needs to be given for theSource-Block in order for any of the other commands to be used.

Command:

Recursive (Yes or No);

Valid In:

Source-Block

Can Be Repeated:

Default:

Description:

AutoRPM will recurse any subdirectories in the source directory or sourceFTP site. The rest of the commands below can be used if set to Yes.

Command:

Recursive_Compare_To_Dir ("path_name");

Valid In:

Source-Block

Can Be Repeated:

Yes

Default:

Description:

If package XXX-1.0-1.i386.rpm is in the /i386/ subdirectory of the server, it mustalso be in the /i386/ subdirectory of path_name to be compared. You can still usethe standard 'Compare_To_Directory' in recursive mode, but then all the local RPMswould have to be in one directory to be compared against any of the source directories.

Command:

Recursive_Copy_After_Install ("path_name");

Can Be Repeated:

Yes

Default:

Description:

Will place a copy of the source RPM into the directory "path_name" after a successfulinstallation. You probably want to remember to use the Delete_After_Install commandto avoid keeping duplicate copies. You can still use the standardcopied into the same local directory regardless of what position in the remotetree the file was.

Command:

Recursive_Store ("path_name");

Valid In:

Action-Block

Can Be Repeated:

Yes

Default:

(don't store)

Description:

Causes whatever source file is new or updated (depending on which action blockthis command is in) to be stored in the given directory. If the source file wasin the 'i386' subdirectory in the Source directory or FTP site, it will be storedin the 'i386' subdirectory of the given path_name (which will be created if necessary).You can still use the regular Store command in Recursive mode, but it will storeall RPMs in the same local directory regardless of what subdirectory it came fromin the source tree...If you are also going to possibly Install this RPM, be sure to give the 'Store'command before the 'Install' command so the RPM won't be transfered twice.

Commands:

Regex_Dir_Ignore ("regex");

Regex_Dir_Accept ("regex");

Valid In:

Source-Block

Can Be Repeated:

Yes

Default:

(accept all)

Description:

These commands tell which directories to recurse. See the section onACCEPT & IGNORE & REGULAR EXPRESSIONS above.

FTP POOLS

FTP Pools are a new concept to AutoRPM starting in version 1.9. The ideais to define a pool that describes what you want (i.e. it might be named`redhat60updates'). There is then a list of FTP sites that provides thesepackages that you want. Every site listed should provide the samething. In other words, don't define an FTP pool and then list a bunchof sites to be checked, as only one of them will be checked each time.

Once you have the pool defined (see below), using the pool is easy. Youjust specify your source block as an `ftppool'. AutoRPM will then automatically take care of picking a site from the pool every time and maintaining a ranking of these sites. The FTP_Retries() command isstill used. If FTP_Retries is set to 5, for example, then every timeAutoRPM is run, it will try to connect to a site from the pool 5 times.If all 5 of those attempts fail, AutoRPM will move on. However, thefailures are noted in the sites' scores and will make them less likelyto be tried again in the future. AutoRPM will also wait the specifiedamount of time (as specified by FTP_Retry_Delay()) between these attempts.

To define a FTP pool, you create a simple text file in the directory/etc/autorpm.d/pools. The name of the text file is the name of the pool.On each line of the text file, you list one FTP site and the directory thatcontains the RPMs. Each line should be in the form "ftp://ftp.somewhere.com/pub/redhat/RPMS/i386", but the older form of "ftp.somewhere.com:/pub/redhat/RPMS/i386" will stillwork as well. If you want to do non-anonymous FTP logins, you may use theform "ftp://user:password@ftp.somewhere.com/pub/redhat/RPMS/i386". If youput passwords in these files, make sure you make then non-public-readable.You can also put variables in the pool file that are expected to have beendefined either in the main /etc/autorpm.d/autorpm.conf or in the file inside of/etc/autorpm.d that is using the FTP Pool. These are in the form${VarName}. They are definied by using Set_Var(), Read_Var() andEval_Var().

On the technical side of things, AutoRPM will maintain a score file inthe `scores' subdirectory of the temp directory (i.e. /var/spool/autorpm/scores)for each FTP Pool. The format of this file is one site per line, with twonumbers following it. The first number is the number of times AutoRPM hassuccessfully connected to this site. The second number is the number of timesAutoRPM has tried to connect to this site. A site's score is determined bydividing the number of successes by the number of tries and getting a percent. Every time AutoRPMuses an FTP Pool, the site with the highest score is used (with ties brokenby random). If there is no existing score for a new entry in an FTP Pool,it is initialized to 1 success and 2 tries, giving it a score of 50%. Thisway, if you have a brand new system and it tries to look for official Red Hat6.0 updates and there are 20 sites in the pool, it will randomly pick one. After one failure to connect and login, that site will drop down to 33%, andanother site will be used for the next attempt. If a login to a siteis successful, but the specified directory doesn't exist or is not accesible,the site's score is dropped to 0% (so this site will never be tried again unless everybody else's scores drop to 0% as well). Finally, when the numberof tried connections to a site reaches a number (currently 20), the valuesfor both the successful and attempted connection counts are both cut in half.This prevents one site from becoming so preferred that it takes weeks to knockit off the top of the list even if the machine had been smashed to piecesand is never coming back.

AUTHOR

Kirk Bauer <kirkAATTkaybee.org>

http://www.kaybee.org/~kirk

ftp://ftp.kaybee.org/pub/redhat/RPMS

AutoRPM Mailing Lists:

autorpm-announceAATTkaybee.org

autorpmAATTkaybee.org

autorpm-develAATTkaybee.org

Send bug reports and suggestions to: autorpmAATTkaybee.org.

Index

NAME
SYNOPSIS
DESCRIPTION
FILE FORMAT
ARGUMENTS
MAIN FILE & BLOCKS
REPEATED COMMANDS
ACCEPT & IGNORE COMMANDS & REGULAR EXPRESSIONS
MAIN-FILE COMMAND SUMMARY
SOURCE-BLOCK COMMAND SUMMARY
ACTION-BLOCK COMMAND SUMMARY
RECURSION COMMANDS
FTP POOLS
AUTHOR
SEE ALSO

This document was created byman2html,using the manual pages.

AUTORPM.CONF

NAME

SYNOPSIS

DESCRIPTION

FILE FORMAT

ARGUMENTS

MAIN FILE & BLOCKS

REPEATED COMMANDS

ACCEPT & IGNORE COMMANDS & REGULAR EXPRESSIONS

MAIN-FILE COMMAND SUMMARY

SOURCE-BLOCK COMMAND SUMMARY

ACTION-BLOCK COMMAND SUMMARY

RECURSION COMMANDS

FTP POOLS

AUTHOR

SEE ALSO

Index