Hi,
is there any particular (technical) reason why the fix for ITS4664 (dynlist memleak) has not been included in 2.3.28? I was just wondering how big/serious that leak is, since I'm in the process of upgrading our servers from 2.3.27 to 2.328 and I might as well include the dynlist.c from HEAD. Although they've been running on 2.3.27 with dynlist since its release and we haven't experienced any memory shortages yet.
Kind regards, Michael Heep
Hi,
is there any particular (technical) reason why the fix for ITS4664 (dynlist memleak) has not been included in 2.3.28? I was just wondering how big/serious that leak is, since I'm in the process of upgrading our servers from 2.3.27 to 2.328 and I might as well include the dynlist.c from HEAD. Although they've been running on 2.3.27 with dynlist since its release and we haven't experienced any memory shortages yet.
The fix to ITS#4664 has not been included essentially because dynlist is a minor component of OpenLDAP, and the leak was not that serious. Furthermore, there was no real push about that.
If your message came in before the release of 2.3.28, maybe the fix would have made it into the release.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati@sys-net.it ------------------------------------------
openldap-software@openldap.org