On Thu, 13 Feb 2020 15:05:57 +0100 Matus UHLAR - fantomas wrote: > >On Wed, 12 Feb 2020 18:03:01 +0000 (UTC) > >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 > >> > >> 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... Thanks! > > On 13.02.20 12:30, RW wrote: > >Bayes doesn't write on scans (unless it does an opportunistic sync or > >expiry): > > doesn't it record token access times to journal?
I meant it doesn't write to a database file. The main point of the journal is that it bypasses reader-writer locking.
