An example configuration may be found in the directory
The tests are defined using one or more configuration files
located in the directory
Typically, there is a file called
tests.conf, but any other name would be
All files found in this directory are analyzed.
For each test, a section like
[ethernet_eth0] classes = cs:admin testsets = reboot:prologue test = /opt/parastation/lib/checks/ethernet eth0 100 timeout = 10 killwait = 2 [md5sum_parastation_cs] classes = cs testsets = reboot test = /opt/parastation/lib/checks/md5sum /etc/parastation/classes/cs/md5sums [md5sum_parastation_admin] classes = admin testsets = reboot test = /opt/parastation/lib/checks/md5sum /etc/parastation/classes/admin/md5sums
Figure 4.2. Example
is required. The strings in brackets define a test name and start a new section decribing the named test.
The following list numerates all parameters. They may be given
in any order within a test section of the configuration file.
Parameter and value are separated by an
A colon separated list of classes this test belongs to.
A colon separated list of test sets this test belongs to.
Command to be executed. Everything right of the equal sign is passed as-is to bash's eval.
Timeout for the test in seconds. If the
timeout is reached before the
test returns, a signal
sent to the process and it is handled as if it returned an
Time to wait between
SIGKILL in case the
timeout of the test is reached.
The ordering of the tests within the configuration file defines the ordering the tests are run afterwards.
Within the previous example, three tests called
md5sum_parastation_admin are defined.
ethernet_eth0 is related to the
It is part of the test sets
The check itself is performed using the command
/opt/parastation/lib/checks/ethernet using the
For information about the required parameters, take a look at
the check itself.
The check will be terminated after
timeout seconds using signal SIGTERM.
killwait seconds, it will be killed