>    I'm running SpamAssassin 3.0.2 on an OpenBSD 3.6-STABLE machine,
> on an AMD64 3000+ with 2GB of RAM.  I have yet to see this machine
> even touch the second gig of RAM, and it's never been into swap.
>
>    This is a new server, so I'm trying to train Bayes using a corpus
> I've been saving for a while.  Unfortunately, I seem to have found
> an issue with sa-learn (or perhaps sa-learn and OpenBSD):
>
> [EMAIL PROTECTED] ~]$ sa-learn --showdots --spam --dir
> /home/benny/Maildir/.SPAM.corpus.2004.archive15/cur/
> ...................................................................
> ...................................................................
> ......Out of memory!
>
>    This failure is reproducable every time, on the exact same message.
> When sa-learn fails in this manner, it also fails to clean up its
> lock file (although, I suppose that's to be expected if it's the OS
> that's killing it), presenting a minor DoS situation for future
> sa-learn runs.
>
>    I have increased my limits to the same level as system daemons and
> root, to no effect.  As a test, I tried running the exact same command
> as root, and got the same "Out of memory!" error.  I went through the
> SpamAssassin source, and I don't find this error, so I'm thinking it's
> OpenBSD clamping down on sa-learn for some reason.

For the archives' benefit, I'm replying to my own post.

I seem to have figured this problem out - an old version of HTML::Parser
was installed.  Why the hell I installed an outdated version on a new
server build, I have no idea.

However, something that vexes me is the fact that '-D --lint' showed the
versions for several perl modules, but _not_ HTML::Parser.  If it had,
I probably would have figured this out two weeks ago.  :(

Is there a logical reason it's not displayed?  Or is it an oversight?
If the latter, can it please be added before the next dope like me
comes along with an outdated module?  :)

Thanks!

Benny


-- 
"I'm so Goth, my wrists slit themselves."
                                                  -- bash.org

Reply via email to