On Wed, 11 Jan 2006, [EMAIL PROTECTED] stipulated:
> From: "Chris" <[EMAIL PROTECTED]>
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>> I run SA 3.1 on a home system which gets about 200 - 250 msgs a day, the
>> majority being spam of course. I have 768mb of ram with
>> a swap of 612mb,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 11 January 2006 9:10 pm, jdow wrote:
> On 2.64 I'm not sure what's the forking process. It may be modestly
> painful. But an extra 3 seconds every hour and a half is no big tax
> to pay on your machine's performance unless you're trying to
On 2.64 I'm not sure what's the forking process. It may be modestly
painful. But an extra 3 seconds every hour and a half is no big tax
to pay on your machine's performance unless you're trying to play
precision timing games in the background. Heck, you could run raw
spamassassin and not really se
On Wednesday 11 January 2006 7:06 pm, jdow wrote:
> From: "Chris" <[EMAIL PROTECTED]>
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > I run SA 3.1 on a home system which gets about 200 - 250 msgs a day,
> > the majority being spam of course. I have 768mb of ram with a swap of
> > 6
From: "Chris" <[EMAIL PROTECTED]>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I run SA 3.1 on a home system which gets about 200 - 250 msgs a day, the
majority being spam of course. I have 768mb of ram with a swap of 612mb,
an AMD Sempron 1.6GHz processor. This is how spamd is started fro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I run SA 3.1 on a home system which gets about 200 - 250 msgs a day, the
majority being spam of course. I have 768mb of ram with a swap of 612mb,
an AMD Sempron 1.6GHz processor. This is how spamd is started from
the /etc/rc.d/init.d/spamassassin
