Langue: en

Autres versions - même langue

Version: July 2008 (fedora - 01/12/10)

Section: 5 (Format de fichier)


arm4.conf - ARM 4 agent configuration file




The agent has a number of configurable options that are controlled through the configuration file. The agent and it's utilities can use either the default file at /etc/arm4.conf, or a file passed in as a command line argument. While the options are passed to the programs as they start, they generally affect persistent global objects shuch as the shared memory regions that remain after the program exits. Because of this, many options will only be changed when the shared memory objects are recreated.
Options may be set in one of two ways:
<option> <value>
<option> = <value> Blank lines and lines starting with # are considered to be comment lines. The different configuration options are:
overrides the default hostname. The default value is the same as returned by running the command uname -n.
the user name or UID for the daemon. The defaults is to run as the current user.
the group name or GID for the daemon. The defaults is to run as the current group.
the umask used for the creation of shared objects.
specify the ARM 4 instance number. Refer to user guide for more information on running multiple instances. The default instance is 0.
specify a file that will log all error messags from the the arm4_daemon process.
specify a location for the schema files. This may be a local directory or a URL. This does not include the name of the schema file itself.
specify the database to use as the back end. The supported back ends are bdb for Berkeley databases, and sqlite for Sqlite3 databases.
the home directory for the ARM 4 instance databases. The default is /var/lib/arm4/data.
the parent directory for the database archives. When a new archive is created, a time stamped directory is created as a child of this directory. The default is /var/lib/arm4/data/backup.

Berkeley DB Specific Configuration Options

sets the transaction file size for the Berkeley DB. This should be large enough that no single transaction can span multiple files or memory allocation errors will occur. The db_file_size parameter must always be smaller than the db_buffer_size. Refer to the Berkeley DB documentation for more information.
sets the size of memory allocated for transactions. It should be large enough to hold all active transactions or memory allocation errors will occur. the db_buffer_size parameter should always be larger than db_file_size. Refer to the Berkeley DB documentation for more information.
multiple instances of the Berkeley database share common memory regions. In cases where this is undesireable, the db_key can be set explicitly. Refer to the Berkeley DB documentation for more information.
specifies the database checkpoint interval in seconds. A value less than or equal to zero disables checkpointing, except on database close. It is also possible to initiate a checkpoint operation using arm4_control(1).




Report bugs at <> Copyright © 2005-2008 David Carter <> and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at


arm4_daemon(1), arm4_control(1), arm4_dump(1), arm4_export(1) arm4_report(1)