diff options
author | Denys Vlasenko <dvlasenk@redhat.com> | 2011-05-10 02:08:58 +0200 |
---|---|---|
committer | Denys Vlasenko <dvlasenk@redhat.com> | 2011-05-10 02:08:58 +0200 |
commit | c9120cdc51ce7aba5a19500bf24692144ac64983 (patch) | |
tree | 0ea3eea23f1f68bca3b40e50e64616e7885b5d75 /doc | |
parent | 752b264ed8b08a59e60894b310bad522585674e9 (diff) | |
download | abrt-c9120cdc51ce7aba5a19500bf24692144ac64983.tar.gz abrt-c9120cdc51ce7aba5a19500bf24692144ac64983.tar.xz abrt-c9120cdc51ce7aba5a19500bf24692144ac64983.zip |
Do away with reanalyze events
Now code determines whether analyze event can be skipped
by looking at <creates-elements>backtrace</creates-elements>
element in .xml file.
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/design | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -71,8 +71,8 @@ can trigger their initial ("post-create") processing themselves] Crashes conceptually go through "events" in their lives. Apart from "post-create" event decribed above, they may have -"analyze" event, "reanalyze" event, "report[_FOO]" events, -ans arbitrarily-named other events. +"analyze" event, "report[_FOO]" events, +and arbitrarily-named other events. abrt-handle-crashdump tool can be used to "run" an event on a directory, or to query list of possible events for a directory. /etc/abrt/abrt_event.conf file describes what should be done on each event. |