> > >I've been seeing the following in my logs since upgrading to SA 2.63 > > >Mar 1 16:07:54 troll spamd[15918]: Cannot open bayes databases > > >/etc/mail/spamassassin/files/bayes_* R/W: tie failed: Permission denied > > >Mar 1 16:07:54 troll spamd[15918]: Cannot open bayes databases > > >/etc/mail/spamassassin/files/bayes_* R/W: tie failed: Permission denied > > >t > > > > > >I have set 'bayes_auto_learn 0' so it theory spamd shouldn't > > want a R/W tie > > >to toks and seen... I'm sure it didn't usedto. Is there any way > > of getting > > >spamd to only go for a R/O tie or do I have to change my > > permissions to get > > >rid of these annoying log messages? > > > > > > SA ties the bayes DB for r/w in the following situations: > > 1) learning > > 2) forgeting > > 3) token expiry > > 4) journal synchronization. > > > > > > disabling autolearn deals with #1. > > #2 never occurs automatically. > > #4 only occurs if you use the learn_to_journal option > > > > But #3 will happen automatically in a default install. > > > > You need to set bayes_auto_expire to 0. > > > > WARNING: if you set bayes_auto_expire to 0, you should call sa-learn > > --force-expire on a regular basis (ie: a daily cron job). > > > Aha! Top stuff..... that has indeed fixed the problem. Arg! No it hasn't! A few min after I added 'bayes_auto_expire 0' and restarted.... they started turning up in my logs again :/ Could SA be trying to sync the journal? I know that last-access times are noted in there.... Also, I'm not using learn_to_journal and I'm running sa-learn manually for now (it will end up being scripted). Any more ideas?
Nick
