From: Tim W. <tim...@gm...> - 2004-12-07 13:36:08
|
On Tue, 7 Dec 2004 14:11:17 +0100 (CET), Yves <yme...@pe...> wrote: > > > > When perfparsed breaks, if you can find the reason, tell us, and we'll try to find a way > to make perfparsed do something else than break. well, whenever there is a problem with one of the storage modules, it simply exits: e.g. if the db is unavailable or (like I had this morning) the filesystem where the db resides is full. Last week I tried to use the file_output and mysql storage modules, but the file_output module would not load (haven't figured out why yet, it just said "storage_file_output module failed to initialize itself"). In all these cases, perfparsed exited. The question of course is, what should perfparsed do? Should it exit or not? I don't think there's a simple answer to that, except that in case of failure, I'd like to know about it :) One place I look at is the error log. The things I'd like to add to the error log is some extra info when a module is succesfully initialised, a bigger buffer for error messages (they get truncated at 256 chars), and a clear 'perfparsed stopped' message whenever there is a fatal error. Tim. > > Yves > -- > - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - > - GPG key - http://ymettier.free.fr/gpg.txt - > - Maitretarot - http://www.nongnu.org/maitretarot/ - > - Perfparse - http://perfparse.sf.net/ - > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Perfparse-users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-users > |