On Monday 04 October 2004 23:24, Jerry Glomph Black wrote: > Good enough argument, but the new version has killed off > two machines that have successfully run SA/spamd with no > problems since Jan 2002. > > The machines leak into oblivion, and Something Bad > happens (major daemons killed off, etc.). > > There is definitely some kind of memory resource problem > (if not an outright leak) going on. Which reverting to > the old fork-on-demand -might- help.
Perhaps code to say, "What's my present memory usage?" when it starts up, and a periodic "Hmm my memory usage has grown by 20%. time to die." Or perhaps a config entry/commandline parameter that says filter a hundred messages then croak. In the mean time, how about an hourly cronjob that kills and restarts spamd E.g: /usr/local/bin/spamd -r /var/run/spamd.pid -d Crontab entry: 0 * * * * root "kill -HUP `cat /var/run/spamd.pid` -- Sherwood Botsford St. John's School of Alberta
