Milter-greylist

Jim Carroll a \ufffdcrit :
> We've noticed that over time (and in our configuration), the memory
> consumption of milter-greylist has grown to over 400 MB per server instance.
> [...]
> In the long run, perhaps the best approach is to refactor the code to use a
> char* for r_addr, and malloc() new entries based on the actual length of the
> address.

Our milter-greylist currently eats up to 2GB. This is not a problem for 
now since our server has plenty of RAM (16GB), but since we compiled it 
in 32-bit, it may some day hit the 4GB-limit of per-process address 
space. So optimization would not hurt...

By the way, our database holds only 35000 entries; could there be some 
memory leak ? hmmm..


-- 
Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.