Have had two Gamera-servers running for about 6 months now and the filter email with great success.

However, I have noticed that only around 250MB of the RAM is being used, and the machines got 1GB of mem. The load is sometimes up to 10-12, but mem never exeed 250 megs.

The maillogs also shows notices about...



... and I guess that's why memory never raises. How can I start spamd with flags like this? Running the command:


gives:



Also, what would a good number be?

Could be OS related, what distro are you on?

Running Centos 4.3 with your ASL kernel. What I also have seen is that log rotation seams to be problematic. After a few days /var/log/messages is empty, and new items are being logged into /var/log/messages.1

After a reboot this are being propery logged into messages log. Can't think of anything other then ASL that might cause this. Running APF, have mounted /tmp as noexec etc. but nothing that would affect the system itself.

Centos 4.2 + ASL however seamed to work perfect, after updating to 4.3 it just doens't feel as stable as it shoud.

Sidenote, mounting /tmp noexec isn't really necessary on an ASL box, the whole system is already noexec when you use it.

The syslog issue sounds unrelated to memory use, but if logrotate was screwed up, it would cause the problems you're having. The process it follows is:
stop syslog
move log file
start syslog

Im guessing that the stop part isn't working.

Running two diffrent boxed with CentOS 4.3 + ASL (one for DNS and one for Gamera) and the logrotate problem seams to be on both these boxes. The Gamera box have been running for about 6 months, but only with ASL for about a week or so. The DNS-box is completely new with fresh CentOS 4.3 + ASL just a few weeks ago.

Changed logotate to daily i /etc/logrotate.conf and ran:

/usr/sbin/logrotate /etc/logrotate.conf

and then looked at the logs and they looks fine. New items are beeing logged into messages, maillog etc and not messages.1... So running the command as root directly works, but the cron set up to do the same thing seams to fail?!

Mounting /tmp as noexec is just an old habit. It feels good