Revision as of 14:36, 31 March 2010

Description

This test case tests the functionality of the ABRT plugins.

Go thru the config files /etc/abrt/plugins/*.conf and look for line:

Enabled = yes

How to test this: only plugins with this line in their config file should be loaded by abrt daemon

# service abrtd stop
# abrtd -d

and you should see what is being Registered and then try to fiddle with enabled plugins

ABRT should behave according to the configuration options.

@@ Line 3: / Line 3: @@
 |actions=
-Edit config file  /etc/abrt/abrt.conf, where you should find lines:
+Go thru the config files /etc/abrt/plugins/*.conf and look for line:
 <pre>
-# enabled plugins
+Enabled = yes
-EnabledPlugins = SQLite3, CCpp, Logger
 </pre>
-How to test this: only plugins in EnabledPlugins are loaded, so try to run
+How to test this: only plugins with this line in their config file should be loaded by abrt daemon
 <pre>
-# service abrt stop
+# service abrtd stop
-# abrt -d
+# abrtd -d
 </pre>
-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.
+and you should see what is being '''Registered''' and then try to fiddle with enabled plugins
-Database Plugin:
-<pre>
-# selected DB plugin
-Database = SQLite3
-# this option is to ensure, that crashdumps won't take the whole HDD space
-MaxCrashReportsSize = 1000
-</pre>
-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.
 |results=