Rev 192 | Blame | Compare with Previous | Last modification | View Log | RSS feed
EVENT=post-create type=vmcore remote!=1(# If kdump machinery already extracted dmesg...if test -f vmcore-dmesg.txt; then# ...use thatabrt-dump-oops -u $DUMP_DIR vmcore-dmesg.txt || exit $?## Does "kernel" element exist?test -f kernel && exit 0## Try creating it from vmcore-dmesg.txt:# MCE oopses don't have kernel version in them,# but it should be specified earlier in the log.k=`sed -n '/Linux version/ s/.*Linux version \([^ ]*\) .*/\1/p' vmcore-dmesg.txt | tail -n1`test "$k" != "" && printf "%s" "$k" >kernelelse# No vmcore-dmesg.txt, do it the hard way:abrt-action-analyze-vmcore || exit $?## Does "kernel" element exist?test -f kernel && exit 0## Try creating it from dmesg_log (created by abrt-action-analyze-vmcore):test -f dmesg_log || exit 0k=`sed -n '/Linux version/ s/.*Linux version \([^ ]*\) .*/\1/p' dmesg_log | tail -n1`test "$k" != "" && printf "%s" "$k" >kernelfi)# Do not fail the event (->do not delete problem dir)# if check-oops-for-hw-error exits nonzero:{ abrt-action-check-oops-for-hw-error || true; }{ abrt-action-check-oops-for-alt-component || true; }# analyzeEVENT=analyze_VMcore type=vmcoreabrt-action-analyze-oops &&abrt-action-save-package-data# 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 type=vmcorereporter-kerneloops# reportEVENT=report_Kerneloops type=vmcorereporter-kerneloopsEVENT=report_Bugzilla type=vmcorereporter-bugzilla -b \-F /etc/libreport/plugins/bugzilla_format_kernel.conf# update ABRT database after successful report to bugzillaEVENT=post_report type=vmcorereporter-ureport -A -B# Send micro reportEVENT=report_uReport type=vmcore/usr/libexec/abrt-action-ureportEVENT=report-gui type=vmcorereport-gtk -- "$DUMP_DIR"EVENT=report-cli type=vmcorereport-cli -- "$DUMP_DIR"