I don't know for sure but Alex Broens aka axb is a master at Bayes with
Redis.  Definitely look for his postings.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Wed, Feb 12, 2020 at 2:02 PM Pedro David Marco <pedrod_ma...@yahoo.com>
wrote:

> Fully aligned with my suspicions...
>
> I love Redis...  i think someone posted sometime ago a performance table
> showing local / sql / redis  ... i will look for it...
>
> but it would not surprise me if remote Redis is even faster than local
> DB...
>
> Thanks! Ďakujem mnohokrát Fantomas!
>
> Pedro.
>
>
> On Wednesday, February 12, 2020, 7:32:42 PM GMT+1, Matus UHLAR - fantomas <
> uh...@fantomas.sk> wrote:
>
>
> On 12.02.20 18:03, Pedro David Marco wrote:
> >i am getting  errors from Byes because it is not able to lock Bayes
> files...
> >Error log is:
> >  bayes: cannot open bayes databases /etc/spamassassin/bayes/bayes_* R/W:
> lock failed: Interrupted system call
> >
> > SA tries to lock bayes files always in "EXclusive mode", hence when a sa
> takes too long, all other processes have to wait for the lock...
> >
> >This is my config:
> >use_bayes 1bayes_path /etc/spamassassin/bayes/bayesbayes_auto_learn
> 0bayes_auto_expire 0lock_method flock
>
> this is your problem. bayes is designed for one user. not for all of them.
> If you want, you can move bayes database to SQL or to redis, but I don't
> recommend that for multiuser machine.
> For a single-user, bayes database can be simply in your
> $HOME/.spamassassin/
>
>
> >SA uses EXclusive lock because it has "to write"...  my question is...
> > Is there any way to avoid SA writing Bayes files?  in that case a
> > non-exclusive lock would be enough...
>
> no.
>
> --
> Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
> Warning: I wish NOT to receive e-mail advertising to this address.
> Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
> Spam is for losers who can't get business any other way.
>
>

Reply via email to