From Fedora Project Wiki

(clean up)
 
(One intermediate revision by one other user not shown)
Line 2: Line 2:
 
|description=
 
|description=
 
This test case tests EVENT configuration in ABRT.
 
This test case tests EVENT configuration in ABRT.
 
 
|actions=
 
|actions=
# Create file /etc/abrt/events.d/processes.conf with content:
+
# Create a file {{filename|/etc/abrt/events.d/3rd-party.conf}} with content:
#:<pre>EVENT=post-create ps auxf > /tmp/process.crash.`date +"%Y-%m-%d_%H:%M:%N"`</pre>
+
#:<pre>EVENT=post-create echo "Custom 3rd party configuration was used" > /tmp/3rd-party-notice.$(date +"%Y-%m-%d_%H:%M:%N")</pre>
# Restart ABRT deamon
+
# Restart abrtd: {{command|su -c 'systemctl restart abrtd.service'}}
# Crash some aplication
+
# Crash a running application with {{command|kill -SIGSEGV (pid)}} or {{command|pkill -SIGSEGV (processname)}}
 
 
 
|results=
 
|results=
# A file /tmp/process.crash.* for each application crash is created and contains the output of ps auxf command.
+
# A file 3rd-party-notice.* with text above should exist in /tmp
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Latest revision as of 20:53, 29 March 2011

Description

This test case tests EVENT configuration in ABRT.


How to test

  1. Create a file /etc/abrt/events.d/3rd-party.conf with content:
    EVENT=post-create echo "Custom 3rd party configuration was used" > /tmp/3rd-party-notice.$(date +"%Y-%m-%d_%H:%M:%N")
  2. Restart abrtd: su -c 'systemctl restart abrtd.service'
  3. Crash a running application with kill -SIGSEGV (pid) or pkill -SIGSEGV (processname)

Expected Results

  1. A file 3rd-party-notice.* with text above should exist in /tmp