Dennis Duval wrote:
I have to restart spamd within a couple of minutes after restarting syslogd
with the init script or it will crash the system. However doing a
killall -HUP syslogd has no affect on spamd and it continues logging. I
know of no other applications that would crash a system as a r
Justin Mason wrote:
> Dennis Duval writes:
>> Morris Jones wrote:
>>> I've never had a problem like this, of course. But I
>>> wonder what you might discover if you turned debugging
>>> on for spamd? Start it with the -D flag?
>>>
>> Thanks to Justin Mason and Tom Meunier for pointing out
>> the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dennis Duval writes:
>Morris Jones wrote:
>> I've never had a problem like this, of course. But I
>> wonder what you might discover if you turned debugging on
>> for spamd? Start it with the -D flag?
>>
>Thanks to Justin Mason and Tom Meunier for po
Morris Jones wrote:
> I've never had a problem like this, of course. But I
> wonder what you might discover if you turned debugging on
> for spamd? Start it with the -D flag?
>
Thanks to Justin Mason and Tom Meunier for pointing out the -m option and
the FAQ on this questions. Last night, I remo
-m 15 will limit it to 15 spamd instances. Give that a shot.
I'm kinda surprised by how quickly this happens, though.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Dennis Duval
> Sent: Monday, November 03, 2003 5:05 PM
> To: [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
"Dennis Duval" writes:
>I'm new to spamassassin and I'm having a serious problem. The problem is
>that the number of running spamd instances suddenly start increasing
>dramatically until the point all memory and swap space are used up, thus
>locking
