On 2015-05-24 23:25 +0200, Mark Martinec wrote:
Mark> With other bayes back-ends the traditional expiration mechanisms
Mark> need to be used, either auto-expiration runs triggered from time
Mark> to time by SpamAssassin, or explicit expiration runs, e.g. from a
Mark> cron job. With these traditional back-ends the bayes_token_ttl
Mark> setting has no effect.
On 24.05.15 15:26, Ian Zimmerman wrote:
Perhaps this paragraph could be included verbatim in the podfile, and
the current wording (especially about bayes_auto_expire) removed :-)
maybe re-worded, not removed.
But, in fact I already have a cronjob running "sa-learn
--force-expire". The reason I would prefer to remove it (and so the
reason for my original post) is that it does a journal sync as well,
which I didn't intend and which interferes with other things.
what other things? Journal is here to fasten database updates, not to avoid
database writes. too big journal slows things down.
The main reason to use manual expire is to avoid ocassional delays with
automatic expire noted in the bugreport you posted link to.
so, again, what are reasons you want to avoid journal syncs?
--
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.
It's now safe to throw off your computer.
