Milter-greylist

<attila.bruncsak@...> wrote:

> 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.

I guess someone could incrementally try each developement snapshot to
between 3.0 and 4.0 alpha to see when things went wrong. But that's not
a funny job. :-/

The other option is to use specialized tools for tracking down memory
leaks. Any specialist here? Someone that could perform a Coverity run on
the sources?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...