Subversion Repositories configs

Rev

Details | Last modification | View Log | RSS feed

Rev Author Line No. Line
192 - 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
#
17
# EVENT=post-create
18
#
19
#         cp /etc/example.conf .
20
#         uptime > uptime
21
#         echo $HOSTNAME `uname -r`
22
#
23
# This example event will copy `/etc/example.conf` to newly created
24
# problem directory, store current uptime in `uptime` file
25
# and prints current hostname and uname to logs.
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.
31
# Each rule 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
34
# word "EVENT" or a name of problem directory element to be checked
35
# (for example, "executable", "package", hostname" etc).
36
#
37
# If all conditions match, the remaining part of the rule
38
# (the "program" part) is run in the shell.
39
# All shell language constructs are valid.
40
# All stdout and stderr output is captured and passed to abrt
41
# and possibly to abrt's frontends and shown to the user.
42
#
43
# If the program terminates with nonzero exit code,
44
# the event processing is considered unsuccessful and is stopped.
45
# Last captured output line, if any, is considered to be
46
# the error message indicating the reason of the failure,
47
# and may be used by abrt as such.
48
#
49
# If the program terminates successfully, next rule is read
50
# and processed. This process is repeated until the end of this file.
51
 
52
include events.d/*.conf
53
include workflows.d/*.conf
54
 
55
# For testing purposes only
56
#EVENT=report_Dummy type=libreport echo "Hello world" >> /tmp/libreport.log
57
 
58
EVENT=report-gui type=libreport
59
    report-gtk -- "$DUMP_DIR"
60
 
61
EVENT=report-cli type=libreport
62
    report-cli -- "$DUMP_DIR"