Sorry, I intended to included this entry from the messages log: Apr 10 00:00:02 msop sendmail[1622]: unable to dlopen /usr/lib/sasl2/libcrammd5.so.2: /usr/lib/sasl2/libcrammd5.so.2: failed to map segment from shared object: Cannot allocate memory
Thanks, Joey -----Original Message----- From: Richard Frovarp [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 11, 2007 9:51 AM To: Joey Davis Cc: users@spamassassin.apache.org Subject: Re: Spamassassin and memory utilization Joey Davis wrote: > I am running into memory allocation problems and am not sure how to > resolve it. My question: Is it advisable to limit the number of child > processes started by spamassassin in my situation. I'm green and not > sure how to handle this. > > I am on a VPS with thirty email users. > > > Tasks: 21 total, 2 running, 19 sleeping, 0 stopped, 0 zombie > Cpu(s): 0.0% us, 0.0% sy, 0.0% ni, 100.0% id, 0.0% wa, 0.0% hi, > 0.0% si, 0.0% st > Mem: 4139312k total, 3961724k used, 177588k free, 53200k buffers > Swap: 8388576k total, 592k used, 8387984k free, 3245160k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 1 root 16 0 1916 668 576 S 0 0.0 0:00.07 init > 4002 root 16 0 1580 564 472 S 0 0.0 0:01.15 syslogd > 4010 root 16 0 4900 1108 792 S 0 0.0 0:00.00 sshd > 4019 root 15 0 2144 828 700 S 0 0.0 0:00.61 xinetd > 5166 sa-milt 19 0 2240 524 404 S 0 0.0 0:00.00 > spamass-milter- > 5167 sa-milt 16 0 44804 1512 1108 S 0 0.0 0:05.74 > spamass-milter > 5187 root 16 0 27484 9420 5852 S 0 0.2 0:00.10 httpd > 5196 root 16 0 3128 1116 576 S 0 0.0 0:00.02 crond > 5204 root 16 0 5148 1280 984 S 0 0.0 0:00.02 saslauthd > 5210 apache 16 0 27640 5096 1432 S 0 0.1 0:00.32 httpd > 5324 apache 15 0 27640 5104 1432 S 0 0.1 0:00.35 httpd > 5346 apache 15 0 27640 5080 1400 S 0 0.1 0:00.35 httpd > 20384 root 16 0 46880 43m 2220 S 0 1.1 0:03.25 spamd > 15603 apache 16 0 27620 5096 1400 S 0 0.1 0:00.23 httpd > 15694 apache 15 0 27756 5116 1400 S 0 0.1 0:00.26 httpd > 15582 root 15 0 54044 50m 2272 S 0 1.2 1:45.61 spamd > 21824 root 16 0 48016 44m 2204 S 0 1.1 0:02.25 spamd > 10082 jdavis 16 0 7212 2692 2188 S 0 0.1 0:00.07 imapd > 11463 root 16 0 7896 2384 1936 R 0 0.1 0:00.11 sshd > 11481 root 15 0 2432 1372 1104 S 0 0.0 0:00.04 bash > 15631 root 16 0 2056 988 796 R 0 0.0 0:00.01 top > Yes, it probably would be advisable to limit the number of child processes. However, I don't see any indication there that you are running into memory problems.
