# This table specifies which programs should be run
# when the specified event occurs in crash dump lifetime.
#
# Example:
# EVENT=post-create   { pwd; date; }>/tmp/dt; echo $HOSTNAME `uname -r`
#
# Each line may have conditions to be checked
# before the program is run.
#
# Conditions have form VAR=VAL, where VAR is either word "EVENT"
# or a name of crash dump element to be checked (for example,
# "executable", "package", hostname" etc).
#
# If all conditions match, the program 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 exitcode,
# 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 line is read
# and processed. This process is repeated until the end of this file.

# abrt-action-analyze-c needs package name, save package data first
EVENT=post-create                       abrt-action-save-package-data
EVENT=post-create analyzer=CCpp         abrt-action-analyze-c
EVENT=post-create analyzer=Python       abrt-action-analyze-python
EVENT=post-create analyzer=Kerneloops   abrt-action-analyze-oops
# If you want all users (not just root) to be able to see oopses:
#EVENT=post-create analyzer=Kerneloops  echo 1 >inform_all_users
# If you want behavior similar to one provided by kerneloops daemon
# distributed by kerneloops.org - that is, if you want
# oopses to be reported automatically and immediately without
# user interaction, uncomment this line:
#EVENT=post-create analyzer=Kerneloops  abrt-action-kerneloops
# Example: if you want to save sosreport immediately at the moment of a crash:
#EVENT=post-create  nice sosreport --tmp-dir "$DUMP_DIR" --batch --only=anaconda --only=bootloader --only=devicemapper --only=filesys --only=hardware --only=kernel --only=libraries --only=memory --only=networking --only=nfsserver --only=pam --only=process --only=rpm -k rpm.rpmva=off --only=ssh --only=startup --only=yum && { rm sosreport*.md5; mv sosreport*.tar.bz2 sosreport.tar.bz2; mv sosreport*.tar.xz sosreport.tar.xz; true; } 2>/dev/null

#TODO: implement this (or add this functionality to abrt-action-install-debuginfo):
#EVENT=analyze analyzer=CCpp backtrace=  trim-debuginfo-cache /var/cache/abrt-di 4096m
# Additional directories to search for debuginfos can be specified
# in the third argument (its format is CACHEDIR[:DEBUGINFODIR...]).
# For example, you can specify a network-mounted shared store
# of all debuginfos this way.
EVENT=analyze analyzer=CCpp backtrace=   abrt-action-install-debuginfo "$DUMP_DIR/coredump" "/var/run/abrt/$$-$RANDOM" /var/cache/abrt-di
EVENT=analyze analyzer=CCpp backtrace=   abrt-action-generate-backtrace

# Same as "analyze", but executed when user requests "refresh" in GUI
#EVENT=reanalyze analyzer=CCpp  trim-debuginfo-cache /var/cache/abrt-di 4096m
EVENT=reanalyze analyzer=CCpp   abrt-action-install-debuginfo "$DUMP_DIR/coredump" "/var/run/abrt/$$-$RANDOM" /var/cache/abrt-di
EVENT=reanalyze analyzer=CCpp   abrt-action-generate-backtrace

EVENT=report          analyzer=Kerneloops  abrt-action-kerneloops
EVENT=report_Bugzilla analyzer=CCpp        abrt-action-bugzilla -c /etc/abrt/plugins/Bugzilla.conf
EVENT=report_Logger   analyzer=CCpp        abrt-action-print -o /var/log/abrt.log
EVENT=report_Bugzilla analyzer=Python      abrt-action-bugzilla -c /etc/abrt/plugins/Bugzilla.conf
EVENT=report_Logger   analyzer=Python      abrt-action-print -o /var/log/abrt.log