No edit summary |
No edit summary |
||
Line 26: | Line 26: | ||
How to test this: set this to some lower value and try to generate some crashdumps with abrt and | How to test this: set this to some lower value and try to generate some crashdumps with abrt and | ||
exceed this limit - the last dump shouldn't be saved | exceed this limit - the last dump shouldn't be saved. | ||
Note - the last saved dump can exceed this value, but the next one won't | |||
be saved | be saved. | ||
|results= | |results= |
Revision as of 14:56, 19 August 2009
Description
This test case tests the functionality of the ABRT plugins.
How to test
Edit config file /etc/abrt/abrt.conf, where you should find lines:
# enabled plugins EnabledPlugins = SQLite3, CCpp, Logger
How to test this: only plugins in EnabledPlugins are loaded, so try to run
# service abrt stop # abrt -d
and you should see what is being loaded and try to fidle with enabled plugins -- if you remove SQLite3 plugin it should complain that it needs some DB plugin.
Database Plugin:
# selected DB plugin Database = SQLite3 # this option is to ensure, that crashdumps won't take the whole HDD space MaxCrashReportsSize = 1000
How to test this: set this to some lower value and try to generate some crashdumps with abrt and exceed this limit - the last dump shouldn't be saved. Note - the last saved dump can exceed this value, but the next one won't be saved.
Expected Results
ABRT should behave according to the configuration options.