[EMAIL PROTECTED] wrote:
So a few times a day I end up having to stop my sendmail on my linux mail
server. Here is the back story. I was running 2.64, with procmail and
recently upgraded to 3.1. I started the 3.1 with
/usr/bin/spamd -d -c -m10
Which works great, but I think the old spamassassin is still running because
when the 10 children get filled up, I start to get a ton of:
/usr/bin/spamc
Whats going on here? 2 versions running? What do I do to get rid of the
spamc process, and keep it from spawning and then bringing my server to its
knees...
Well, if in fact, your spamd is really busy, and it can't accept more
connections, spamc may be waiting around to try again. I'm not 100%
positive on the behavior of spamc (I use my own app to connect to spamd
from 'doze.) The way mine works, is it will try again after a few
seconds of waiting. This may be the cause here. One way to find out if
you have more than one version is to search the system for all
references to any spamd/c/assassin and check the versions. This is very
tedious, but it gets the end result. If when you do /usr/bin/spamc -V
what do you get? Along with /usr/bin/spamd -V and the same for
spamassassin (where you have that installed also.) The do spamc -V,
spamd -V, spamassassin -V and see what the system 'thinks' the path is
to the programs.
What you describe, to me, seems a normal action when all the connections
are filled.
Then again, I could be completely wrong :-D
--
Thanks,
JamesDR
