summaryrefslogtreecommitdiffstats
path: root/libreport/src/lib/report_event.conf
diff options
context:
space:
mode:
Diffstat (limited to 'libreport/src/lib/report_event.conf')
-rw-r--r--libreport/src/lib/report_event.conf47
1 files changed, 0 insertions, 47 deletions
diff --git a/libreport/src/lib/report_event.conf b/libreport/src/lib/report_event.conf
deleted file mode 100644
index a99ce8ab..00000000
--- a/libreport/src/lib/report_event.conf
+++ /dev/null
@@ -1,47 +0,0 @@
-# This configuration file specifies which programs should be run
-# when the specified event occurs in dump directory lifetime.
-#
-# It consists of directives and rules.
-#
-# Directives start with a reserved word. Currently, there is only one
-# directive, "include". Its format is "include FILE".
-# It causes files which match FILE to be read and
-# parsed as if they are inserted textually where this directive
-# occurs. FILE can use shell pattern metacharacters (*,?,etc) to
-# specify multiple files. Relative paths are interpreted relative
-# to current file.
-#
-# Rule starts with a line with non-space leading character.
-# All subsequent lines which start with space or tab form one rule.
-# Note that separating newline is *retained*. Example:
-# EVENT=post-create date >/tmp/dt # semicolon is not needed here!
-# echo $HOSTNAME `uname -r`
-#
-# Rules may be commented out with #. One # is sufficient to comment out
-# even a multi-line rule (no need to comment out every line).
-#
-# Rules specify which programs to run on the dump directory.
-# Each rule may have conditions to be checked before the program is run.
-#
-# Conditions have form VAR=VAL or VAL~=REGEX, where VAR is either
-# word "EVENT" or a name of dump directory element to be checked
-# (for example, "executable", "package", hostname" etc).
-#
-# If all conditions match, the remaining part of the rule
-# (the "program" part) is run in the shell.
-# All shell language constructs are valid.
-# All stdout and stderr output is captured and passed to abrt
-# and possibly to abrt's frontends and shown to the user.
-#
-# If the program terminates with nonzero exit code,
-# the event processing is considered unsuccessful and is stopped.
-# Last captured output line, if any, is considered to be
-# the error message indicating the reason of the failure,
-# and may be used by abrt as such.
-#
-# If the program terminates successfully, next rule is read
-# and processed. This process is repeated until the end of this file.
-
-include events.d/*.conf
-
-EVENT=report_Dummy analyzer=libreport echo "Hello world" >> /tmp/libreport.log