No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
|actions= | |actions= | ||
Edit config file | Edit config file ''/etc/abrt/abrt.conf'', where you should find lines: | ||
<pre> | <pre> | ||
# list of actions and reporters which are activated immediately after a | # list of actions and reporters which are activated immediately after a | ||
| Line 15: | Line 15: | ||
<pre>ActionsAndReporters = RunApp("ls", "ls-output")</pre> | <pre>ActionsAndReporters = RunApp("ls", "ls-output")</pre> | ||
Saves output from ''ls'' command to file called ''ls-output''. This file will be used in summary report. Try Reporter plugin Mailx(<subject>) or other. | |||
Now let's go through second section. There is saved association among analyzers and actions and/or reporter plugins: | Now let's go through second section. There is saved association among analyzers and actions and/or reporter plugins: | ||
<pre> | <pre> | ||
[ AnalyzerActionsAndReporters ] | [ AnalyzerActionsAndReporters ] | ||
# all C/C++ | # all C/C++ crashes will be reported via Logger plugin | ||
CCpp = Logger | CCpp = Logger | ||
# if bind | # if bind crashes, then an email will be send and Logger (from ''CCpp'' section) should be silent | ||
CCpp:bind = Mailx("[abrt] Bind crashed") | CCpp:bind = Mailx("[abrt] Bind crashed") | ||
# all kernel crashers will be reporter via Logger | # all kernel crashers will be reporter via Logger | ||
| Line 28: | Line 28: | ||
</pre> | </pre> | ||
How to test this: try to change the analyzer - reporter association to | How to test this: try to change the analyzer - reporter association to something else and report some crash. | ||
it should | it should report somewhere else (Logger logs to /var/log/abrt-logger, Mailx sends email to the configured email address). | ||
|results= | |results= | ||
Verify that the command ''ls'' was run and it's output | Verify that the command ''ls'' was run and it's output is in ''ls-output''. | ||
}} | }} | ||
[[Category:ABRT_Test_Cases]] | [[Category:ABRT_Test_Cases]] | ||
Revision as of 10:46, 19 August 2009
Description
This is testing ABRT Actions and Reporters
How to test
Edit config file /etc/abrt/abrt.conf, where you should find lines:
# list of actions and reporters which are activated immediately after a crash # occurs ActionsAndReporters =
If you add here some reporter or action plugin, then it shout be run at crash time. So for example:
ActionsAndReporters = RunApp("ls", "ls-output")
Saves output from ls command to file called ls-output. This file will be used in summary report. Try Reporter plugin Mailx(<subject>) or other.
Now let's go through second section. There is saved association among analyzers and actions and/or reporter plugins:
[ AnalyzerActionsAndReporters ]
# all C/C++ crashes will be reported via Logger plugin
CCpp = Logger
# if bind crashes, then an email will be send and Logger (from ''CCpp'' section) should be silent
CCpp:bind = Mailx("[abrt] Bind crashed")
# all kernel crashers will be reporter via Logger
Kerneloops = KerneloopsReporter
How to test this: try to change the analyzer - reporter association to something else and report some crash. it should report somewhere else (Logger logs to /var/log/abrt-logger, Mailx sends email to the configured email address).
Expected Results
Verify that the command ls was run and it's output is in ls-output.