> I did see that a number of memory leaks have been fixed since
2.4.30, b=
ut I
> didn't see anything that looked like this profile. Sorry I
don't have =
a newer
> version of OpenLDAP to hand to re-test.
Closing this ITS. You can followup again if you see the same problem in t=
he=20
current 2.4.41 release candidate. 2.4.30 is over 3 years old, no one
is g=
oing=20
to investigate this.
I wasn't asking anyone to look into 2.4.30. Given how easy this is to test=
, Howard,
and in the interests of code hygiene, wouldn't it be better for you to spen=
d 10 minutes
attempting to reproduce the problem on the latest RC? It'll take me much l=
onger to
download and compile the new RC than it would do for you to import a bad en=
try and
set-up basic syncrepl. If, by doing so, you can identify and fix another m=
emory leak
then that's a really good thing. If you can't reproduce it in 2.4.41 after=
10 minutes, then
I understand if you close the issue.
Best regards,
Mark.
---------------------------------------------------------------------------=
-----
NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinion=
s or views contained herein are not intended to be, and do not constitute, =
advice within the meaning of Section 975 of the Dodd-Frank Wall Street Refo=
rm and Consumer Protection Act. If you have received this communication in =
error, please destroy all electronic and paper copies; do not disclose, use=
or act upon the information; and notify the sender immediately. Mistransmi=
ssion is not intended to waive confidentiality or privilege. Morgan Stanley=
reserves the right, to the extent permitted under applicable law, to monit=
or electronic communications. This message is subject to terms available at=
the following link:
http://www.morganstanley.com/disclaimers. If you canno=
t access these links, please notify us by reply message and we will send th=
e contents to you. By messaging with Morgan Stanley you consent to the fore=
going.=