Quoting Ross Boylan (rossboy...@stanfordalumni.org): > I also encountered severe memory leak in samba 3.4 backported to lenny. > I backported by compiling from source, pulling in various sid > dependencies as needed. I installed with > # dpkg -i samba-common_3.4.3-1_all.deb > samba-common-bin_3.4.3-1_i386.deb samba-doc-pdf_3.4.3-1_all.deb > samba_3.4.3-1_i386.deb libsmbclient_3.4.3-1_i386.deb > smbclient_3.4.3-1_i386.deb > > Within 2 days smbd had consumed over 2G of memory, bringing the system > to a crawl. Unfortunately, other processes got killed by the kernel. > > I realize this is not a supported configuration, but thought it was > worth a report.
Certainly. However, we (pkg maintainers) are not really in position to help that much here, except by acting as proxies with upstream. Are you in position to report this in upstream's Bugzilla (https://bugzilla.samba.org) so that you can investigate this deeper directly with them? It would also be good if someone could check a similar situation with an unstable machine.
signature.asc
Description: Digital signature
