Well, I figured that, but why. It never did this before.  Is it possible that a rule causes a loop and forces SA to shutdown?

On 10/26/06, Daryl C. W. O'Shea <[EMAIL PROTECTED]> wrote:
Juan Mas wrote:
> Im getting this odd behavior where spamd shuts itself down out of
> nowhere.  I cant really pinpoint what makes it shutdown just what Ive
> found in the logs.

> spamd[27466]: [spamd] fork: Cannot allocate memory at /usr/bin/spamd

I'd say that's a pretty good reason for it to stop working.

Daryl




--
-Juan

Reply via email to