On Wednesday 05 of September 2012 12:50:36 Denys Vlasenko wrote:
> On 09/05/2012 12:25 PM, Denys Vlasenko wrote:
> > I think just putting the script into the ccpp_retrace_event.conf
>
> > is slightly better:
> Regarding "sensitive data warning". It can be in the event too,
>
> this allows us to go to local analyzing if used says "no":
> > EVENT=analyze_RetraceServer analyzer=CCpp
>
> echo "ASK_YES_NO" "`gettext "Ok to upload core dump? (It may
> contain sensitive data)"`" read answ
> test x"$answ" = x"yes" &&
Cool. I like it. How do we store user's answer in this case? Because we probably don't want to ask user in every run of reporting
>
> > abrt-retrace-client batch --dir "$DUMP_DIR" --status-delay 10
> > if test $? != 0; then
>
> #
> # We are here if user chose 'no', or if retrace client failed.
> #
>
> > echo "ASK_YES_NO" "`gettext "Do you want to perform analysis
> > locally?"`"
> > read answ
> > test x"$answ" = x"yes" || exit 1
> > #
> > # Similar/same as analyze_LocalGDB:
> > #
> > abrt-action-analyze-core --core=coredump -o build_ids &&
> > /usr/libexec/abrt-action-install-debuginfo-to-abrt-cache
> > --size_mb=4096 &&
> > abrt-action-generate-backtrace
> >
> > fi &&
> > abrt-action-analyze-backtrace &&
> >
> > ...