You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Lucas Albers <ad...@cs.montana.edu> on 2004/07/30 19:23:57 UTC
[Fwd: Re: Bayes.pm: oops! still tied to Bayes DBs, untie'ing]
I think I got over this problem by doing bayes learn to journal.
---------------------------- Original Message ----------------------------
Subject: Re: Bayes.pm: oops! still tied to Bayes DBs, untie'ing
From: "Ryan Thompson" <ry...@sasknow.com>
Date: Fri, July 30, 2004 12:36 am
To: spamassassin-users@incubator.apache.org
--------------------------------------------------------------------------
I believe I've fixed this now.
For a better description, and my proposed fix:
http://bugzilla.spamassassin.org/show_bug.cgi?id=3651
- Ryan
Ryan Thompson wrote to spamassassin-users@incubator.apache.org:
>
> Hi all,
>
> Since moving to MIMEDefang, I'm getting "oops! still tied to Bayes DBs,
untie'ing" quite frequently (a few hundred times a day or so). It occurs
fairly predictably when MIMEDefang is restarted, but also occurs during
normal use.
>
> I did look at the relevant code in Bayes.pm (3.0.0-pre2), and it seems
like this isn't a critical problem, but are there any solutions to
eliminate the problem (and the log spam)? If this really isn't a big
deal, I might be inclined to just comment out the warning. :-)
>
> Thanks,
> - Ryan
>
>
--
Ryan Thompson <ry...@sasknow.com>
SaskNow Technologies - http://www.sasknow.com
901-1st Avenue North - Saskatoon, SK - S7K 1Y4
Tel: 306-664-3600 Fax: 306-244-7037 Saskatoon
Toll-Free: 877-727-5669 (877-SASKNOW) North America
--
Luke Computer Science System Administrator
Security Administrator,College of Engineering
Montana State University-Bozeman,Montana
Re: [Fwd: Re: Bayes.pm: oops! still tied to Bayes DBs, untie'ing]
Posted by Ryan Thompson <ry...@sasknow.com>.
Lucas Albers wrote to mimedefang@lists.roaringpenguin.com:
> > > Since moving to MIMEDefang, I'm getting "oops! still tied to Bayes
> > > DBs, untie'ing" quite frequently (a few hundred times a day or so).
> > > It occurs fairly predictably when MIMEDefang is restarted, but also
> > > occurs during normal use.
> >
> > For a better description, and my proposed fix:
> > http://bugzilla.spamassassin.org/show_bug.cgi?id=3651
>
> I think I got over this problem by doing bayes learn to journal.
In my case, learning to journal didn't help (in fact, that's how I had
things configured from the start), as SA still had to tie to the seen
and toks databases in compile_now().
A workaround would probably be to comment out the "compile_now()" call
in mimedefang-filter, though the one-line patch to SA will allow you to
benefit from the efficiency of compile_now() without the useless
warning.
- Ryan
--
Ryan Thompson <ry...@sasknow.com>
SaskNow Technologies - http://www.sasknow.com
901-1st Avenue North - Saskatoon, SK - S7K 1Y4
Tel: 306-664-3600 Fax: 306-244-7037 Saskatoon
Toll-Free: 877-727-5669 (877-SASKNOW) North America