> > I couldn't say if I have it, as my milter is restarted every > 24 hours by > a crontab. A safety net that should not exist for a beta, but > was actually > very useful for earlier developement versions. > > I wouldn't be surprised if we had a memory leak somewhere. > At my side the version 3.0 was running fine in production for 5 months without restarting. There is no sign of any significant memory leek. If you wish I can provide the log of the command: ps vax | grep /usr/local/bin/milter-greylist | grep -v grep >> /var/milter-greylist/runningsize.log That is scheduled to run from crontab once an hour. I stopped the milter-greylist v3.0 just to participate in the 4.O alpha testing. Otherwise it would still run fine I am convinced. Bests, Attila
Message
RE: [milter-greylist] version 4.0a4 aborts with message: "mg_setreply(): invoked twice"
2007-05-15 by attila.bruncsak@itu.int