[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

A. Where GNATS lives

We use a few conventions when referring to the installation structure GNATS uses. These values are adjustable when you build and install GNATS (see section Installing GNATS).

A.1 prefix  
A.2 exec-prefix  
A.3 The `gnats-adm' directory  
A.4 Default installation locations  

[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

A.1 prefix

prefix corresponds to the variable `prefix' for configure, which passes it on to the `Makefile' it creates. prefix sets the root installation directory for host-independent files as follows:

database-specific configuration and database contents

site-wide configuration files

man pages

info documents

include files


The default value for prefix is `/usr/local', which can be changed on the command line to configure using

configure --prefix=prefix ...

See section Configuring and compiling the software.

[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

A.2 exec-prefix

exec-prefix corresponds to the variable `exec-prefix' for configure, which passes it on to the `Makefile' it creates. exec-prefix sets the root installation for host-dependent files as follows:

GNATS user tools

administrative and support utilities

compiled libraries


configure supports several more options which allow you to specify in great detail where different files are installed. The locations given in this appendix do not take into account highly customized installations, but fairly ordinary GNATS installations should be covered by the material here. For a complete list of options accepted by configure, run ./configure --help in the `gnats' subdirectory of the distribution.

Since most installations are not intended to be distributed around a network, the default value for exec-prefix is the value of `prefix', i.e., `/usr/local'. However, using exec-prefix saves space when you are installing a package on several different platforms for which many files are identical; rather than duplicate them for each host, these files can be shared in a common repository, and you can use symbolic links on each host to find the host-dependent files.

Use exec-prefix in conjunction with prefix to share host-independent files, like libraries and info documents. For example:

   for each host:
configure --prefix=/usr/gnu --exec-prefix=/usr/gnu/H-host
make all install ...

Using this paradigm, all host-dependent binary files are installed into `/usr/gnu/H-host/bin', while files which do not depend on the host type for which they were configured are installed into `/usr/gnu'.

You can then use a different symbolic link for `/usr/gnu' on each host (`/usr' is usually specific to a particular machine; it is always specific to a particular architecture).

  on host-1:
ln -s /usr/gnu/H-host-1 /usr/gnu
  on host-2:
ln -s /usr/gnu/H-host-2 /usr/gnu

To the end user, then, placing `/usr/gnu/bin' in her or his PATH simply works transparently for each host type.

You can change exec-prefix on the command line to configure using

configure --exec-prefix=exec-prefix ...

We recommend that you consult section `Using configure' in Cygnus configure, before attempting this.

[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

A.3 The `gnats-adm' directory

Each GNATS database located on a server has its own directory, as listed in the `databases' (see section The databases file and given when the mkdb utility is invoked to initialize the database (see section Initializing a new database). This directory has several subdirectories, one of which is named `gnats-adm'. This directory contains all configuration files related to this specific database, including the `categories', `submitters', `responsible', `states', `classes', `dbconfig', `addresses', `states' and `gnatsd.access', as well as two files generated and maintained by GNATS, `index' and `current'.

[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

A.4 Default installation locations

defaults to `/usr/local'; change using configure (see section Configuring and compiling the software).

defaults to prefix; change using configure (see section Configuring and compiling the software).

GNATS installs tools, utilities, and files into the following locations.


See section Submitting Problem Reports.
See section Editing existing Problem Reports.
See section Querying the database.


See section Timely reminders.

See section Checking database health.

Tool for deleting PRs. Deprecated. Use the --delete-pr option of pr-edit instead (see section The edit-pr driver).

See section The diff-prs tool.

See section Interface to pr-edit for filing new PRs.

See section Regenerating the index.

The GNATS daemon.

See section Converting old password files.

See section Setting up mail aliases.

See section Adding a problem category.

See section Script for creating new databases.

See section The pr-age tool.

See section The main PR processor.

See section Handling incoming traffic.

See section Removing categories.

The GNU libiberty library.


The list of valid databases. For local databases it contains the pathname of the database directory, and for remote databases it has the hostname and port of the gnatsd server to connect to. (see section The databases file).

A directory containing the set of default files used when a new database is created with mkdb. (see section The dbconfig file).

The access-level settings for the different hosts that will be accessing the databases on your server. The settings in this file apply across all databases on the server. See section The `gnatsd.host_access' file.

The access-level settings for the users that will be accessing the databases on your server. The settings in this file apply across all databases on the server. See section The `gnatsd.access' file.


The Emacs versions of the programs send-pr, query-pr, edit-pr, and view-pr. See section The GNATS user tools. To change this directory you must change the lispdir variable in `Makefile.in'; see Configuring and compiling the software.


The GNATS manuals, in a form readable by info (the GNU hypertext browser). See section `Reading GNU Online Documentation' in GNU Online Documentation.


man pages for all the GNATS tools and utilities.
See section The GNATS user tools.

Per-database directory

Administration and configuration data files that define behaviour of the particular database. The files










(This file is created by GNATS.)

(This file is created by GNATS.)

exist here. See section GNATS configuration, Administrative data files and Controlling access to databases.

Incoming Problem Reports are queued here until the next iteration of `queue-pr -r' (see section Handling incoming traffic).

If no default category is set, problem reports without a category are reassigned to the category `pending' and placed here pending intervention by GNATS administrators. See section GNATS administration.

Each valid category has a corresponding subdirectory in the database. All Problem Reports associated with that category are kept in that subdirectory.

[ << ] [ >> ]           [Top] [Contents] [Index] [ ? ]

This document was generated by Yngve Svendsen on January, 9 2002 using texi2html