I've got my bayes database files in a tmpfs filesystem and I wanted to
back them up every hour via cron so that I would have something to start
from in the event of a system crash, so I wrote a script to lock and copy
them and I decided to throw in a db_verify just to be sure I had a good
copy. Wha
Perhaps I spoke too quickly when I suggested that the bayes
expiry code must be broken. I finally read David Lee's message
carefully and realized that the expiry code might be getting timed
out by mimedefang or sendmail and interrupted before it has time to
complete. I should have read it earlier b
The issue is that bayes expiry is broken under some circumstances
as evidenced by this listing of my bayes database area, possibly
because its taking more than 10 minutes, or possibly because there
is a bug in the code
-rw--- 1 defang defang32 Jan 26 12:19 bayes.lock
-rw--- 1
In an earlier posting I pointed out that I had noticed that a
db_verify on bayes_toks frequently yields errors of the form
db_verify: Page 2289: hash page has bad prev_pgno
db_verify: Page 2110: hash page has bad prev_pgno
and I asked if I should just ignore the errors since bayes seemed
to b
