Bayes Rebuild not happening

[Eric Dantan Rzewnicki]

Nevermind. I found it in the latest beta release. So ... lines 127-145
should look like this?:

        # Do the actual expiry run
        MailScanner::Log::InfoLog('SpamAssassin Bayes database rebuild starting');
        eval {
          $MailScanner::SA::SAspamtest->init(1);
          $MailScanner::SA::SAspamtest->init_learner({
                          force_expire => 1,
                          learn_to_journal => 0,
                          wait_for_lock => 1,
                          caller_will_untie => 1});
          $MailScanner::SA::SAspamtest->rebuild_learner_caches({
                          verbose => 0,
                          showdots => 0});
          $MailScanner::SA::SAspamtest->finish_learner();
        };
        MailScanner::Log::WarnLog("SpamAssassin Bayes database rebuild " .
                                  "failed with error: %s", $@)
          if $@;



-Eric Rz.

On Fri, Mar 26, 2004 at 10:53:07AM -0500, Eric Dantan Rzewnicki wrote:
> Where does the matching } for that eval go?
>
> -Eric Rz.
>
> On Fri, Mar 26, 2004 at 03:34:32PM +0000, Julian Field wrote:
> > Wonderful! At long last we can actually get an error report. That extra
> > eval{} was definitely worth it!
> >
> > Rather than having to get a patch from the SA guys, please can you try this
> > patch to SA.pm
> >
> > -----SNIP-----
> > --- SA.pm.old   2004-03-26 15:33:56.000000000 +0000
> > +++ SA.pm       2004-03-26 15:35:24.000000000 +0000
> > @@ -128,6 +128,7 @@
> >          # Do the actual expiry run
> >          MailScanner::Log::InfoLog('SpamAssassin Bayes database rebuild
> > starting');
> >          eval {
> > +          $MailScanner::SA::SAspamtest->init(1);
> >            $MailScanner::SA::SAspamtest->init_learner({
> >                            force_expire => 1,
> >                            learn_to_journal => 0,
> > -----SNIP-----
> >
> > init() is supposed to be a non-public method, but I can't see any other way
> > of doing it.
> >
> > Let me know if this fixes the problem. If it does, it will go in the next
> > release.