Re: [Samba] Possible Samba Memory Leak

[Andreas Wrede]

I found this thread while researching what probably is the identical problem: smbd processes grow to 200+ Mb size after 10 to 20 hours and crashing. Has any progress been made on resolving it since the last post?

        
On Nov 4, 2005, at 9:54 , Stephen Borrill wrote:

On Thu, 3 Nov 2005, Jeremy Allison wrote:

Here is the last one just before the machine ran out of swap (this process had around 116MB allocated, IIRC). None of these numbers are that big (and if the numbers are in bytes surely they are negligable). The thing that is

changing over time is the number of "passdb internal SAM_ACCOUNT

backend=tdbsam.

allocation" entries. This machine is running security=user with passdb

exactly are you running again ? Where did you get the source code ?

already fixed it and can give you the patch.

Ok, looks like a passdb leak (I hate that interface :-). What version I want to do a diff against the latest SAMBA_3_0 SVN to see if we've

as 3.0.14.

Further to my previous reply, 3.0.20b seems to exhibit the same behaviour

and tell me exactly what you're doing to reproduce the leak ?

Thanks for following up on this, I've been busy with other things but this is still on my list to look at. Can you post me the smbcontrol pool detail output from 3.0.20b (as this is a much more modern code base than 3.0.14a)

Hmm. smbcontrol <pid> pool-usage just returns 0 with 3.0.20b here, so
that's not a lot of use.


domain running. The clients are mapping a drive and then just using it

the mapped drive.

--
Stephen

The clients are Windows 2000 machines running in a workgroup. The samba server is running security=user with passdb backend=tdbsam. There is no throughout the day. They are run a DOS-based FoxPro database (AIUI) from

--
    aew

PGP.sig
Description: This is a digitally signed message part

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba