Ariel wrote:
List, this is normal? Spamd is killing my serverCpu(s): 43.7% us, 7.9% sy, 0.0% ni, 30.1% id, 18.2% wa, 0.0% hi, 0.0% si Mem: 2075128k total, 1813664k used, 261464k free, 198980k buffers Swap: 522104k total, 164k used, 521940k free, 1046028k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 19948 vpopmail 16 0 38812 33m 2704 S 11.3 1.7 0:57.46 spamd 20118 vpopmail 16 0 41720 36m 2716 S 9.2 1.8 1:01.58 spamd 19946 vpopmail 17 0 39932 34m 2364 S 8.9 1.7 1:04.07 spamd 29595 named 21 0 93492 56m 2020 S 3.9 2.8 10:54.12 named 458 vpopmail 18 0 6292 3632 1992 S 1.5 0.2 0:00.05 pyzor 459 vpopmail 18 0 7348 3632 1992 S 1.5 0.2 0:00.05 pyzor 464 vpopmail 19 0 7692 3636 1992 S 1.5 0.2 0:00.05 pyzor 20119 vpopmail 16 0 40452 34m 2360 S 0.9 1.7 1:00.70 spamd
Depending on what rules you're loading, yes. If you have added all kinds of extra rules, or are using the sa-learn functions and not cleaning up after it then this is normal. You have to remember that for every message that comes in, a spamd process has to be created to process it. And each spamd process will load all of the rules into memory. That's why it's better to block the messages at the SMTP level - so you're not creating spamd processes and hogging resources every time a message comes in.
smime.p7s
Description: S/MIME Cryptographic Signature
