On Mon, Dec 29, 2008 at 23:41, Michael Alan Dorman <mdor...@ironicdesign.com> wrote: > On Mon, 29 Dec 2008 23:21:48 +0000 > j...@jmason.org (Justin Mason) wrote: > >> hmm. What do you have in /var/lib/spamassassin for the scores files? >> they should look like this: >> >> : 183...; ls >> -l /var/lib/spamassassin/3.002006/updates_spamassassin_org/50_scores.cf >> /var/lib/spamassassin/3.002006/updates_spamassassin_org/72_scores.cf >> -rw-r--r-- 1 root root 48928 Dec 29 >> 23:20 /var/lib/spamassassin/3.002006/updates_spamassassin_org/50_scores.cf >> -rw-r--r-- 1 root root 1392 Dec 29 >> 23:20 /var/lib/spamassassin/3.002006/updates_spamassassin_org/72_scores.cf > > Hey, Justin, thanks for the quick response. > > My 50_scores.cf is 48923, so it differs, but close enough. > > In fact, it didn't occur to me immediately, but further investigation > (for lack of a better word for the last rather tense 45 minutes :) seems > to be pointing the finger at sa-compile, rather than the scores. > > I got fixated on 72_scores.cf and totally forgot about 50_scores, which > is why I was thinking scores at first. > > I'll be doing more testing and such, later, but just zapping the > compiled files and restarting the processes seems to have taken care of > it. > > If there's anything in particular you'd like me to do to try and help > track the interaction down, please let me know. I'm using re2c 0.13.5 > on debian amd64 boxes, and am happy to throw some time and resources at > figuring out what's going on.
Does the sa-compile step complete with an exit code of 0? If there are problems with re2c (which has happened in the past) it should exit with !=0. --j.
