On Saturday 02 May 2009, Theo Van Dinter wrote: >bayes_seen is rather irrelevant. >bayes_toks is very binary-oriented, and uses lots of pack() calls. > >There is no SA-based "validity" check for the DB files/data. If you >think the DB file itself is corrupt, you could try the appropriate DBM >tools (db_verify, etc.) The dump/restore method really should have >solved your issue. If you're still having the same problem, I would >say either a) are you sure you're looking at the right DB file, b) do >the dump/restore again and make sure to delete/move the DB file before >restoring, c) make sure the data you're restoring is valid (gigo and >all that). > >On Sat, May 2, 2009 at 2:34 PM, Gene Heskett <[email protected]> wrote: >> Greetings; >> >> 1. The suggestions to rebuild the bayes db didn't make any difference. >> 2. The error complains about the packing format of the db, when as near as >> I can tell, it isn't packed, its plain text, or at least the bayes_seen >> file is. And its nearly 9 megabytes. >> >> bayes_toks, OTOH, is inscrutable. and over 2 megabytes. >> >> Is there a way to check this bayes_toks file for validity, & maybe even >> fix it, or should I just nuke all bayes_* and retrain? >> >> Thanks. >> >> -- >> Cheers, Gene >> "There are four boxes to be used in defense of liberty: >> soap, ballot, jury, and ammo. Please use in that order." >> -Ed Howdershelt (Author) >> Look afar and see the end from the beginning.
-- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If you think the system is working, ask someone who's waiting for a prompt.
