Ok, I got a handle on the situation. But I still got a questions:

When spamd receives a message from spamc does spamd spawn a new spamd
process?

I'm seeing that on my machine.

I'm worried that for some reason spamc is not connecting to the spamd daemon
running, instead spamc spawns a new spamd process for each message causing
unnecessary processing...

/Ian


> I run a Communigate Pro server on Mac OS X. Messages are passed to SA using
> rules. Today it has been running into problems. It grew during the day and
> culminated this night, when I had disable SpamAssassin out of the rules. It
> had been running fine for more than a week until now...
> 
> If I activate the SpamAssassin rule I will within a few seconds have loads
> of spamd and spamc processes running:
> 
> ps -aux | grep spam
> daemon 20673  11.0  0.4    13200   6076  ??  S      0:00.29 perl
> /usr/bin/spamd -x -F0 -u daemon
> root   20669   1.0  0.0     1732    556  ??  S      0:00.06 sh
> /Volumes/Raiden/CommuniGate/scanspam.sh -f Q
> daemon 20598   0.4  0.4    13200   5512  ??  S      0:00.33 perl
> /usr/bin/spamd -x -F0 -u daemon
> root   20672   0.1  0.0     1824    280  ??  S      0:00.01 /usr/bin/spamc
> -d 127.0.0.1 -f
> daemon 16247   0.1  0.5    13144   7144  ??  S      0:06.64 perl
> /usr/bin/spamd -x -F0 -u daemon
> root   20574   0.0  0.0     1732    544  ??  S      0:00.05 sh
> /Volumes/Raiden/CommuniGate/scanspam.sh -f Q
> root   20577   0.0  0.0     1824    268  ??  S      0:00.01 /usr/bin/spamc
> -d 127.0.0.1 -f
> daemon 20578   0.0  0.3    13200   5476  ??  S      0:00.30 perl
> /usr/bin/spamd -x -F0 -u daemon
> root   20594   0.0  0.0     1732    544  ??  S      0:00.04 sh
> /Volumes/Raiden/CommuniGate/scanspam.sh -f Q
> root   20597   0.0  0.0     1824    268  ??  S      0:00.01 /usr/bin/spamc
> -d 127.0.0.1 -f
> root   20599   0.0  0.0     1732    548  ??  S      0:00.06 sh
> /Volumes/Raiden/CommuniGate/scanspam.sh -f Q
> root   20602   0.0  0.0     1824    268  ??  S      0:00.02 /usr/bin/spamc
> -d 127.0.0.1 -f
> daemon 20603   0.0  0.4    13200   5752  ??  S      0:00.47 perl
> /usr/bin/spamd -x -F0 -u daemon
> root   20605   0.0  0.0     1732    548  ??  S      0:00.04 sh
> /Volumes/Raiden/CommuniGate/scanspam.sh -f Q
> root   20611   0.0  0.0     1824    268  ??  S      0:00.00 /usr/bin/spamc
> -d 127.0.0.1 -f
> daemon 20612   0.0  0.4    13200   5744  ??  S      0:00.48 perl
> /usr/bin/spamd -x -F0 -u daemon
> root   20613   0.0  0.0     1732    548  ??  S      0:00.05 sh
> /Volumes/Raiden/CommuniGate/scanspam.sh -f Q
> root   20616   0.0  0.0     1824    268  ??  S      0:00.00 /usr/bin/spamc
> -d 127.0.0.1 -f
> daemon 20617   0.0  0.4    13200   5660  ??  S      0:00.30 perl
> /usr/bin/spamd -x -F0 -u daemon
> root   20618   0.0  0.0     1732    552  ??  S      0:00.05 sh
> /Volumes/Raiden/CommuniGate/scanspam.sh -f Q
> root   20621   0.0  0.0     1824    268  ??  S      0:00.02 /usr/bin/spamc
> -d 127.0.0.1 -f
> daemon 20622   0.0  0.4    13200   5660  ??  S      0:00.34 perl
> /usr/bin/spamd -x -F0 -u daemon
> root   20648   0.0  0.0     1732    552  ??  S      0:00.04 sh
> /Volumes/Raiden/CommuniGate/scanspam.sh -f Q
> root   20651   0.0  0.0     1824    272  ??  S      0:00.00 /usr/bin/spamc
> -d 127.0.0.1 -f
> daemon 20652   0.0  0.4    13200   5756  ??  S      0:00.40 perl
> /usr/bin/spamd -x -F0 -u daemon
> root   20654   0.0  0.0     1732    548  ??  S      0:00.05 sh
> /Volumes/Raiden/CommuniGate/scanspam.sh -f Q
> root   20657   0.0  0.0     1824    272  ??  S      0:00.01 /usr/bin/spamc
> -d 127.0.0.1 -f
> daemon 20658   0.0  0.4    13200   5764  ??  S      0:00.46 perl
> /usr/bin/spamd -x -F0 -u daemon
> root   20661   0.0  0.0     1732    556  ??  S      0:00.05 sh
> /Volumes/Raiden/CommuniGate/scanspam.sh -f Q
> root   20664   0.0  0.0     1824    272  ??  S      0:00.00 /usr/bin/spamc
> -d 127.0.0.1 -f
> daemon 20665   0.0  0.4    13200   5692  ??  S      0:00.28 perl
> /usr/bin/spamd -x -F0 -u daemon
> root   20676   0.0  0.0     1112    196 std  R+     0:00.00 grep spam
> [mail:/etc/mail/spamassassin] root#
> 
> and basically no mail comes through...
> 
> It seems the SA processes won't finish.
> Also should there really be more than one instance of spamd running.
> What is the point of the spamd process in watchdog then?
> 
> /Ian
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: Jabber - The world's fastest growing
> real-time communications platform! Don't just IM. Build it in!
> http://www.jabber.com/osdn/xim
> _______________________________________________
> Spamassassin-talk mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/spamassassin-talk



-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to