Using the arm4 package
======================

The arm4 daemon is set to run out of the box, but there are some configuration
options you should be aware of.

The default configuration file is located at /etc/arm4.conf. 'man arm4.conf'
will give more information on the options available to you.

System Configuration Changes
============================

Unless changed from the default configuration, some of the transaction
parameters won't be passed to the daemon. Add the following to
/etc/sysctl.conf:

  kernel.msgmax = 65536
  kernel.msgmnb = 65536

Failure to do so may result in messages in your system log such as
'Transaction uri msgsnd Invalid argument'

Enabling user access to ARM4
============================

The arm4_daemon has access controlled by the use of groups. A user must be a
member of the arm4 group to have access. To add a user to the group, you
can use the administrative GUIs, or you can run the following as root:

 $ usermod -a -G arm4 <username>

Archiving Data
==============

As installed, data is archived once a day. Data older than 31 days is removed.

This can be customized by modifying the cron script at /etc/cron.daily/arm4.cron.

Datastores
==========

This RPM only supports the Berkeley DB datastore. The default configuration for
Sqlite3 doesn't have all the required options, so it hasn't been built into this
installation.

What do I do if no data is collected?
=====================================

The first thing to do is check the system log. Rather than interrupt the flow of
an application, error messages are sent there.

Where can I get more information?
=================================

http://www.arm4.org/