1arm4.conf(5) ARM 4 File Formats arm4.conf(5)
2
6 arm4.conf - ARM 4 agent configuration file
7
9 /etc/arm4.conf
10
12 The agent has a number of configurable options that are controlled
13 through the configuration file. The agent and it's utilities can use
14 either the default file at /etc/arm4.conf, or a file passed in as a
15 command line argument.
16 While the options are passed to the programs as they start, they gener‐
18 ally affect persistent global objects shuch as the shared memory
19 regions that remain after the program exits. Because of this, many
20 options will only be changed when the shared memory objects are recre‐
21 ated.
22 Options may be set in one of two ways:
24 <option> <value>
25 <option> = <value>
26 Blank lines and lines starting with # are considered to be comment
28 lines.
29 The different configuration options are:
31 hostname
33 overrides the default hostname. The default value is the same as
34 returned by running the command uname -n.
35 user the user name or UID for the daemon. The defaults is to run as
37 the current user.
38 group the group name or GID for the daemon. The defaults is to run as
40 the current group.
41 umask the umask used for the creation of shared objects.
43 instance
45 specify the ARM 4 instance number. Refer to user guide for more
46 information on running multiple instances. The default instance
47 is 0.
48 log_filename
50 specify a file that will log all error messags from the the
51 arm4_daemon process.
52 schema_location
54 specify a location for the schema files. This may be a local
55 directory or a URL. This does not include the name of the schema
56 file itself.
57 db specify the database to use as the back end. The supported back
59 ends are bdb for Berkeley databases, and sqlite for Sqlite3
60 databases.
61 db_home_dir
63 the home directory for the ARM 4 instance databases. The default
64 is /var/lib/arm4/data.
65 db_backup_dir
67 the parent directory for the database archives. When a new ar‐
68 chive is created, a time stamped directory is created as a child
69 of this directory. The default is /var/lib/arm4/data/backup.
70 Berkeley DB Specific Configuration Options
73 db_log_file_size
75 sets the transaction file size for the Berkeley DB. This should
76 be large enough that no single transaction can span multiple
77 files or memory allocation errors will occur. The db_file_size
78 parameter must always be smaller than the db_buffer_size. Refer
79 to the Berkeley DB documentation for more information.
80 db_buffer_size
82 sets the size of memory allocated for transactions. It should be
83 large enough to hold all active transactions or memory alloca‐
84 tion errors will occur. the db_buffer_size parameter should
85 always be larger than db_file_size. Refer to the Berkeley DB
86 documentation for more information.
87 db_key multiple instances of the Berkeley database share common memory
89 regions. In cases where this is undesireable, the db_key can be
90 set explicitly. Refer to the Berkeley DB documentation for more
91 information.
92 checkpoint
94 specifies the database checkpoint interval in seconds. A value
95 less than or equal to zero disables checkpointing, except on
96 database close. It is also possible to initiate a checkpoint
97 operation using arm4_control(1).
98
100 /etc/arm4.conf
101
103 Report bugs at <http://www.arm4.org>
104
106 Copyright © 2005-2008 David Carter <dcarter@arm4.org> and others.
107 All rights reserved. This program and the accompanying materials are
109 made available under the terms of the Eclipse Public License v1.0 which
110 accompanies this distribution, and is available at
111 http://www.eclipse.org/legal/epl-v10.html
112
114 arm4_daemon(1), arm4_control(1), arm4_dump(1), arm4_export(1)
115 arm4_report(1)
116arm4.org July 2008 arm4.conf(5)