The configuration file consists of objects that type is specified by a keyword used inside their names and their specification is limited by braces {}. Currently only one type of objects is permitted and its keyword is action. A keyword that describes type of object must be a single word in a whole line. The same rule is applicable to braces that begin and end an object definition. An generic object definition is shown below:

action

{

...

}

Fields occurred between braces are exactly specified like an order of them. Each field from first six ones in an object definition takes a whole line and has got below form:

keyword=

The first field is id that must be followed by an identifier (number of unsigned long type) of that object. On the second place is delaytime field, that sets a number of seconds which must lapse from creation time of a case, that a given action can be run. The next fields repeatingtime indicate about what period of time the action can be repeated. A next field period helps to specify repeating and occurring of the action. That field is enumeration type. The following values are permissible:

after_death

after_join

after_split

once

Every other value of that field (also empty) is treated as always value.

The last field is program_spec object. It may occur more then one time and its definition is limited by braces {}. The braces and program_spec keyword must occur alone in separate lines. The first field of the object is program which shows path to a program that should be run for the action when the given conditions will be met. The last filed which can occur more then one, obligatory time is name. It specifies a string which must occur at least in one event of a case that the given action may be run for that case. When name fields are more then one, they all must occur in a single event that an action can be run.

A pattern of definition of each object is shown below:

action

{

id=

delaytime=

repeatingtime=

period=

program_spec

{

program=

name=

...

}

...

}

Meaning of individual fields in an object definition is discussed in section "Description" of damcsud.