1REPORT_EVENT.CONF(5)           LIBREPORT MANUAL           REPORT_EVENT.CONF(5)
2
3
4

NAME

6       report_event.conf - configuration file for libreport.
7

DESCRIPTION

9       This configuration file specifies which programs should be run when the
10       specified event occurs in problem directory lifetime.
11
12       It consists of directives and rules.
13
14       Directives start with a reserved word. Currently, there is only one
15       directive, "include".
16
17       include FILE
18           This directive causes files which match FILE to be read and parsed
19           as if they are inserted textually where this directive occurs. FILE
20           can use shell pattern metacharacters (*,?,etc) to specify multiple
21           files. Relative paths are interpreted relative to current file.
22
23       Rule starts with a line with non-space leading character. All
24       subsequent lines which start with space or tab form one rule. Note that
25       separating newline is retained.
26
27       Rules may be commented out with #. One # is sufficient to comment out
28       even a multi-line rule (no need to comment out every line).
29
30       Rules specify which programs to run on the problem directory. Each rule
31       may have conditions to be checked before the program is run.
32
33       Conditions have form VAR=VAL or VAL~=REGEX, where VAR is either word
34       "EVENT" or a name of problem directory element to be checked (for
35       example, "executable", "package", hostname" etc).
36
37       If all conditions match, the remaining part of the rule (the "program"
38       part) is run in the shell. All shell language constructs are valid. All
39       stdout and stderr output is captured and passed to ABRT and possibly to
40       ABRT’s frontends and shown to the user.
41
42       If the program terminates with nonzero exit code, the event processing
43       is considered unsuccessful and is stopped. Last captured output line,
44       if any, is considered to be the error message indicating the reason of
45       the failure, and may be used by abrt as such.
46
47       If the program terminates successfully, next rule is read and
48       processed. This process is repeated until the end of this file.
49

EXAMPLES

51       EVENT=post-create analyzer=Python abrt-action-analyze-python
52
53       EVENT=post-create getent passwd "cat uid" | cut -d: -f1 >username
54

SEE ALSO

56       abrtd(8)
57

AUTHOR

59       Manual page written by Denys Vlasenko <dvlasenk@redhat.com[1]>.
60

NOTES

62        1. dvlasenk@redhat.com
63           mailto:dvlasenk@redhat.com
64
65
66
67LIBREPORT 2.0.9.1                 06/19/2018              REPORT_EVENT.CONF(5)
Impressum