AFS components share the same root directory: /usr/local/afs7
The following example shows a typical directory structure for an AFS installation:
The AFS v7.10 files structure includes the following directories:
- bin is the directory for every AFS v7.10 binaries.
- conf is the directory for configuration files.
- include is the directory for external libraries includes (only used for AFS source code or filter compilation).
- java is the directory for Java files.
- lib is the directory for the AFS v7.10 libraries.
- logs is the directory for every AFS v7.10 log. Some logs (acp*, search*, click*) are execution logs and are logged as database, usable by the Antidot Back Office. The other logs (afs_*.log) are system logs coming from the running daemon (acp, logmanager, or querymanager).
- PaF stands for Pipes and Filters. This directory contains the description of the different pipes and filters used. For more information, see the AFS Configuration Guide.
- reply is the directory for the description of the different services and agents.
- scripts is the directory for the scripts used to drive the daemon, to manage user rights, and so on.
- setup is the internal repository for installation-related data (user, group, directory, and so on).
- share is the directory for the different templates for lighttpd and Apache configuration, models for scripts and necessary data for PaF filters (such as indexing stemming dictionaries, named entity extract training databases, and so on).
- tmp is the directory for temporary storage. Nothing persistent is kept here. Each time the Query Engine is launched, the directory data is reset.
- var is the directory for the process ID of the running daemons. It contains internal data to run the daemons. Each time the Query Engine is launched, the directory data is reset.
If the afs7 directory is a symlink, it will be removed by apt/yum in case of Antidot package uninstallation.