I have had SpamAssassin eating a lot of memory. In order to limit the
damage, I set it up with fairly aggressive ulimits. Unfortunately, that
means I am now also getting this error message. I don't see crashes,
though.
Here is a pared-down version of the script I use to start up spamd:
#!/bin/sh
ulimit -v 204800
ulimit -m 204800
ulimit -n 256
# This is the beef. Try even lower numbers.
# I could not start it at all with ulimit -u 110
ulimit -u 150
perl -T -I lib -w spamd \
--configpath myrules \
--siteconfigpath mapsd.cf \
--helper-home-dir . \
--nouser-config \
--syslog stderr \
--min-children 2 \
--max-spare 5 \
--max-children 40 \
"$@"
The ulmit values are otherwise out of contrib/run-masses but I could not
run spamd at all with the ulimit -u 30 they have.
@Christian: If you signed up for Debian bug reports, only you can
unsubscribe. You should see in the headers with what ID you have
subscribed; I believe you should also see an unsubscribe link there.
/* era */
--
If this were a real .signature, it would suck less. Well, maybe not.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
