On Fri, Oct 10, 2003 at 04:56:11PM +0200, Marco Schn?riger wrote: > -rw-r--r-- 1 root root 49152 Oct 10 16:33 bayes_seen > -rw-r--r-- 1 root root 663552 Oct 10 16:33 bayes_toks > > debug: bayes: no dbs present, cannot scan: /root/.spamassassin/_toks
The file it's looking for does not match the file you have. Later on
it has the right path in the -D listing though... <shrug>
> That still looks pretty good, doesn't it? After that, I do an ls:
>
> [EMAIL PROTECTED] .spamassassin]# ls -al
> total 1276
> drwx------ 2 root root 1024 Oct 10 16:47 .
> drwxr-x--- 8 root root 1024 Oct 10 13:22 ..
> -rw------- 1 root root 1403 Oct 10 12:35 bayes_msgcount
> -rw------- 1 root root 49152 Oct 10 16:47 bayes_seen
> -rw------- 1 root root 663552 Oct 10 16:47 bayes_toks
> The files have exactly the same size. That looks a bit strange for me,
> but I can live with that I think. Now I want to know if there is some
> data in the db:
The upgrade didn't happen, you still have a msgcount file which would
have been removed.
> debug: bayes: no dbs present, cannot scan: /root/.spamassassin/_toks
> debug: Initialising learner
> Use of uninitialized value in numeric lt (<) at
> /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/BayesStore.pm line
> 1281.
Hrm. For some reason, the tie fails, but the code doesn't pick up on
this, which causes the uninitialized value warning.
> Why does "bayes: no dbs present, cannot scan: /root/.spamassassin/_toks"
> appear? Sure, there is no file called _toks! But now, look at this:
A bad bayes_path in your config?
--
Randomly Generated Tagline:
If you want your program to be readable, consider supplying the argument.
-- Larry Wall in the perl man page
pgp00000.pgp
Description: PGP signature
