The configuration file consists of lines. Each line of a configuration file is a single entry - a unit of information which begins from a regular expression that describes OID or a type of the notification expressed as a long integer and taken in square brackets. A generic entry looks as follows:

[regular expression] [day ... HH:MM:SS HH:MM:SS] ... path_to_program1 arg1 ... argN, ..., path_to_programN arg1 ... argN; [day ... HH:MM:SS HH:MM:SS] ... path_to_program1 arg1 ... argN, ..., path_to_programN arg1 ... argN; ...

Not all mentioned above items must occur in each record. A regular expression describing numbers of accepted messages is necessary. It must be taken in square brackets. A next item taken in the same brackets may occur zero or more times. Each such element describes some time range. If information comes in one of such specified time ranges, a part of the line up to the nearest semicolon or all line, if none is present, is accepted and processed. A time range must be defined as short names of days of a week (each name started by a capital) and a range of hours common for all mentioned days. If no day of a week occurs, it means that the range of hours concerns every day. If no time range occurs, it means that information must be always accepted.

A necessary item that must be specified is path to at least one program which should be run. Its arguments may follow after it. The specified programs may be more then one but they must be separated by colons.

path_to_program1 arg1 ... argN, ..., path_to_programN arg1 ... argN

A piece of information started by a possible specification of time ranges and finished with the last program and its arguments, may be only a single record in a given line and it may be ended by a semicolon (it's not necessary). If there are more such record then a obligatory one, they must be separated by colons.