DB corruption within minutes

[Matthias Andree]

Barry Gould <BarryGould at pennysaverusa.net> writes:

> At 04:32 PM 1/11/2003 +0100, Matthias Andree wrote:
>>Barry Gould <BarryGould at pennysaverusa.net> writes:
>>
>> > I've noticed that my goodlist file access timestamp gets updated even if
>> > bogofilter is only updated the spam db.
>>
>>In -u mode, that's fine, because it needs to read the file to evaluate
>>the mail it is presented. What matters for writes is the file
>>modification time stamp, also known as mtime.
>>
>>--
>>Matthias Andree
>
> Sorry, I did mean to say it's the modification time that's getting updated.
>
> This only seems to happen on -u executions, not -s,
> BUT I am fairly sure that -u with spam are still causing the mtime to
> change on the goodlist. (evidence submitted below, note that the message
> was correctly recognized as spam by bogofilter -u)

I think that is expected behaviour currently. For any operation that
registers words, that is, any of -u -s -S -n -N, all data bases are
opened in read/write mode, only omitting all these registering options
will make bogofilter open them in read-only mode. I believe it's an
artifact of the "multiple wordlist" feature that is on the TODO list.

Does this cause any problems for you? Contention when multiple processes
are running at the same time or something?

> for example, now (12:58pm Jan 12), my .bogofilter dir looks like:
> -rw-r--r--    1 root     root      8892416 Jan 12 12:54 goodlist.db
> -rw-r--r--    1 root     root      2912256 Jan 12 12:54 spamlist.db

-- 
Matthias Andree