Here is patch plugging one leak in the LDAP code. I found it by using
'valgrind --leak-check=full /usr/sbin/dhcpd3 -q eth0 eth1 -d' and
starting and stopping dhcpd fairly quickly. I believe it only affect
the static mode, but could be wrong.
--- dhcp3-3.1.0.orig/server/ldap.c 2009-12-20 22:12:47.000000000 +0100
+++ dhcp3-3.1.0/server/ldap.c 2009-12-20 22:20:24.000000000 +0100
@@ -269,6 +269,7 @@
x_strncat (cfile->inbuf, tempbv[i]->bv_val, LDAP_BUFFER_SIZE);
x_strncat (cfile->inbuf, ";\n", LDAP_BUFFER_SIZE);
}
+ ldap_value_free_len (tempbv);
}
item->close_brace = 1;
[José RodrÃguez]
> Hi, any hint to reproduce it?
Using dynamic mode is required, I suspect, to see any serous memory
leak in the LDAP code.
> I'm using the same package in about 150 schools with more than
> 120.000 users and haven't noticed that problem.
> There are schools with only 500 users, but some others have around
> 1500 users. Have you noticed if it happens when you have 1500 users
> or less?
I believe you told me on IRC that you are using static mode in your
setup, which would avoid continuous LDAP requests and probably also
avoid memory leaks in the LDAP code.
I'll run valgrind with dhcpd in dynamic mode for a longer period and
see if I can reproduce the more serious leak problem.
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
