(Untitled)

Jul 08, 2002 14:25

Server problems ( Read more... )

Leave a comment

Comments 6

Spamassassin pathwalker July 8 2002, 16:15:02 UTC
You are running it as the spamd daemon, and the spamc client pair, and not just invoking spamassassin for each incoming mail, right?

If not, try it. It shaves down the CPU and memory usage of spamassassin from amazingly high, to merly somewhat high.

Or, you could always run spamd on another box to spread the load around...

Reply

Re: Spamassassin dluke July 8 2002, 19:57:40 UTC
I'm actually not, because spamd is too fragile and dies easily (and I haven't had time to make it better)...

The actual overhead shouldn't be too great, though thanks to the wonder that is Mach.

Reply

Re: Spamassassin pathwalker July 9 2002, 04:40:10 UTC
I was worried about spamd crashing, so I used daemontools to make sure it stays up.

According to svstat spamd has been up for 1274394 seconds without restarting, so I guess I didn't have to worry as much as I thought...

Reply

Re: Spamassassin dluke July 9 2002, 08:02:49 UTC
... but djb is a crazy-man.

spamd died if I connected to it with telnet and then disconnected (it also died if I nmap'd the box locally).

Reply


pratzsch July 8 2002, 17:55:57 UTC
Sure...you disable perl just as I start experimenting with it on your machine! :)

Hope you get everything back up soon.

Reply

dluke July 8 2002, 19:58:51 UTC
That is because I am an ass.

I should have the RAM installed by this weekend at the latest.

Reply


Leave a comment

Up