On Jan 23, 2008, at 9:54 PM, Steven Stern wrote:
It's finally started to remove tokens, so I think I'm OK. We use SQL
bayes, so it was an easy matter to use
~ delete from bayes_token where atime UNIX_TIMESTAMP();
to clean up the stuff from the future.
But now your bayes_vars table is
Michael Parker wrote:
On Jan 23, 2008, at 9:54 PM, Steven Stern wrote:
It's finally started to remove tokens, so I think I'm OK. We use SQL
bayes, so it was an easy matter to use
~ delete from bayes_token where atime UNIX_TIMESTAMP();
to clean up the stuff from the future.
But now
We had a server go crazy last night and reset its date into August of
2277. In any case, we've resolved that, but now I can't get bayes to
expire.
After the clocks was correctly set, I deleted all tokens that had a
lastupdate in the future, and also removed similar bayes_seen rows. I
then
Steven Stern wrote:
We had a server go crazy last night and reset its date into August of
2277. In any case, we've resolved that, but now I can't get bayes to
expire.
After the clocks was correctly set, I deleted all tokens that had a
lastupdate in the future, and also removed similar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/23/2008 07:35 PM, Matt Kettler wrote:
| Steven Stern wrote:
| We had a server go crazy last night and reset its date into August of
| 2277. In any case, we've resolved that, but now I can't get bayes to
| expire.
|
| After the clocks was
I'm getting this message when I run sa-learn -D:
Can't use estimation method for expiry, something fishy, calculating
optimal atime delta (first pass)
It seems to have just started this week. It displays this message for
quite some time, then goes on normally.
Does anyone know what would
