Am 28.01.2015 um 00:55 schrieb RW:
On Tue, 27 Jan 2015 18:49:23 +0100 Reindl Harald wrote:Am 27.01.2015 um 17:28 schrieb Matus UHLAR - fantomas:nobody expires or updates anything in a hand-maintained bayesthe one you might use, but not without timestampsthe intention of this *global bayes* is *not* to learn or expire anything - the implemented "remove from bayes" method is just remove the message from the corpus folder and type "sa-learn.sh rebuild" when i say "*_auto_*" then i mean that and hence the desired result is not write anything, just don't touch the bayes-db in normal operations and don't waste disk IO bayes_auto_expire 0Setting bayes_auto_expire 0 doesn't imply the database is not going to expired. The recommended way to expire is to turn-off auto-expiry and expire from cron.
don't understand that completly * bayes_auto_expire 0 * which cronjob would expire * hopefully not sa-updatei really mean it serious that this bayes has no record which has to expire at any point of time until i say so for the specific message
that's just because it was a hard work to get around 160000 train messages over 5 onths, most if not all are unliekly to become obsolete and even if we decide to kill spam-spamles older than x months it needs to be done properly to keep the 50% spam / 50% ham ratio which is the reason the bayes works that good compared with autolearning setups where everyone i have seen in the past 8 years became worser each month until classify most ham as spam and let thorugh the real crap
That said, it's not really essential to have atime updates. Without them the tokens would still have reasonably sensible timestamps derived from the received headers of the mail used in training. It wouldn't break expiry if they could be turned-off
if understand you correctly we agree that there is no reason /var can't be mounted read-only?
signature.asc
Description: OpenPGP digital signature
