Thanks guys,
Problem solved now, It was a program called "watchdog" in Plesk which was
the problem. Somehow it is not detecting the status of process and is
starting the process again and again.
Jai
On Jan 14, 2008 11:38 PM, Mike Jackson <[EMAIL PROTECTED]> wrote:
> > My server has 8GB of ram,
My server has 8GB of ram, around 4 GB is currently used by spamassassin
(too many process of /usr/bin/perl -T /usr/local/psa/admin/sbin/spammng
-c -C --max-children=1 start).
Is this normal? Can I somehow limit the process concurrency of
spamassassin or I could limit the amount of RAM it consu
Jai Gupta wrote:
> My server has 8GB of ram, around 4 GB is currently used by spamassassin (too
> many process of /usr/bin/perl -T /usr/local/psa/admin/sbin/spammng -c -C
> --max-children=1 start).
"spammng" is not SpamAssassin. Tell whatever is spawning this process
to limit the number of these
Thanks Jeff,
Some stats could be seen on
http://stats.jaigupta.com/com/jaigupta.com-memory.html and
http://stats.jaigupta.com/com/jaigupta.com-processes.html
spamassassin is using RAM with an linearly increasing rate, if it is not
stopped soon my server will end with its all RAM used by spamassas
Quoting Jai Gupta <[EMAIL PROTECTED]>:
My server has 8GB of ram, around 4 GB is currently used by spamassassin (too
many process of /usr/bin/perl -T /usr/local/psa/admin/sbin/spammng -c -C
--max-children=1 start).
Is this normal? Can I somehow limit the process concurrency of spamassassin
or I
My server has 8GB of ram, around 4 GB is currently used by spamassassin (too
many process of /usr/bin/perl -T /usr/local/psa/admin/sbin/spammng -c -C
--max-children=1 start).
Is this normal? Can I somehow limit the process concurrency of spamassassin
or I could limit the amount of RAM it consumes?
