Re: ldirectord memory leak in Ultramonkey 3

>>>>> On Fri, 14 Apr 2006 10:20:12 +0200, [email protected] (Andreas J. Koenig) said:

>>>>> On Wed, 12 Apr 2006 22:46:58 +0900, "Hideaki Kondo" <[email protected]> said:
 >> Thanks a lot for your information.
 >> Certainly, it's strange.
 >> I intend to continue investigating the cause of the ldirectord memory leak.
 >> I will report it here if the cause is found out.

  > I have new evidence. So far I have only tested on one machine. I could
  > see a memory leak with perl 5.8.4, 5.8.7 and 5.8.8. But the leak was
  > not reproducable with current bleadperl (see man perlhack for a
  > reference to bleadperl).

  > The test installation was running for many hours, so I'm pretty sure
  > that bleadperl has this memory leak fixed. I'll let you know when I
  > find out more.

Another piece in the puzzle: the memory leak in ldirectord that seems
to affect only a minority of users is solvable by upgrading
IO::Socket::INET to 1.31.

Bleadperl solved the bug with this patch:

  Change 26921 by gisle@gisle-ask on 2006/01/23 09:57:10

which was then incorporated into Graham Barr's

  IO 1.23 -- Sat Mar 25 19:28:28 CST 2006

Which in turn fixes the leak also for older affected perls.

My impression is that the memory leak is only plugged, not fixed, but
for users of ldirectord the distinction is of minor importance. The
gist of the newer IO::Socket::INET is that it reduces the number of
calls to getprotobyname/number. On systems where these calls are
leaking, we can now run without being affected by the leak.

-- 
andreas


-- 
Ultra Monkey - http://www.ultramonkey.org/
To UNSUBSCRIBE, email to [email protected], with a body:
unsubscribe ultramonkey-users [email protected]
where "[email protected]" is YOUR email address.