> I upgraded to the new v1.0 of bogofilter (which is more than one
> package, as I have found out) from bogofilter_0.94.4-1_i386. I noticed
> that I wasn't getting my mail (I do not know when the problems began),
> and saw that 3 or 4 bogofilters were in memory. When I killed them,
> others kept spawning (every time procmail recipes were called for a
> message), so I had to remove the bogofilter references in my procmail
> recipe file.
You could use a lockfile to prevent multiple invocations.
> I've tried running bogoutil in all sorts of ways: -d, --db-verify,
> --db-recover, --db-recover-harder, etc. -- and it simply hangs every
> time too, with a small footprint in memory (<1M) and using 0% of CPU. No
> disk activity. No way I can export the tokens now, etc. So I don't know
> if the wordlist.db got corrupted or not.
I assume that you aren't running with BDB transactions enabled.
> NB: It's not at all clear to me that the bogoupgrade script _doesn't_
> take .db files as input (IMO unclear documentation and I've only glanced
> at the perl file, looking for clues); so just in case, I'll give you
> this (possibly completely irrelevant) output:
>
> $ bogoupgrade -i wordlist.db -o foo.db
> Cannot recognize signature [V_8_b1_M7_QZ_Z_H_s_A_0_ _{_].
>
>
> I don't know what you can do with the above sketchy information, but
> that's the best I can come up with right now.
You shouldn't need bogoupgrade to go from 0.94.4 to 1.0.0.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
