> so I figured we'd need to get Thomas some more data. Rather than invent
> it by hand, I figured I'd fix up the dynagumper plugin to work properly.
See
Cool, that is what I've been trying to do with Gump3 on VmGump:
> Oh, and you're now greeted with 100s of lines of error messages if you
> don't have a db connection or a messed up database :-).
Like this? ;-)
http://vmgump.apache.org/gump/gump3/run.log
> Adam, perhaps you could take a pass through the code and point your
> finger at stuff that's messed up or which doesn't make sense? Also, one
> todo that'd be nice to have when building dynagump is to actually have
> long logs stored in the DB. I know you've spent a lot of time on the
> builder plugins. For some reason no build_log properties are being set.
> Could you try and get that running?
Sure.
In return, could you look into the problem above seeking to understand why
these failures cause Gump to fall off IRC, not exit? Are certain plugins not
getting called when another fails? I'm never quite sure how Gump3 copes with
errors.
BTW: Can we fix the schema, or do we need to re-instantiate it?
regards,
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
