[Pkg-samba-maint] DO NOT REPLY [Bug 7020] smbd using 2G memory

samba-bugs at samba.org samba-bugs at samba.org
Wed Jan 6 02:18:58 UTC 2010


------- Comment #32 from jra at samba.org  2010-01-05 20:18 CST -------
Yes, the valgrind output isn't showing anything (only the initial "globals"
being "lost", which is just because we know they have to be around for the
entirity of the program run so leave them to be cleaned up on normal exit).
This means you're only getting the valgrind output from the initial daemons
(and the background printer enumeration daemon).

Try doing this:

valgrind --trace-children=yes --leak-check=full /usr/bin/smbd

allowing the client to run a bit and grow the connected <pid>. Just terminate
the <pid> that is leaking by doing:

kill <pid>

This should cause valgrind to print out the error log for the client connected
pid that is causing a problem.

Is this problem still reproducible by doing a Vista file-based backup ?


Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

More information about the Pkg-samba-maint mailing list