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?
I have
On Sun, 2010-01-03 at 08:30 +0100, Christian PERRIER wrote:
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
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
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
4 matches
Mail list logo
