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