On Sun, 2007-01-21 at 20:46 -0500, Jamie ffolliott wrote: > Hi Andrew, > > I'll work on getting a valgrind log during off-hours and get back to you. > > For now I've got some pool-usage output after the daemon's been running > almost 24hrs since last restart. After the number of failures we've been > through now, it's hard to convince others here to allow samba to run long > enough to hit another failure. But the memory does steadily increase, and > it's when it reaches around 260MB that it will consistently begin to fail. > > I noticed most of the structures in there are this one: > struct passwd contains 76 bytes in 6 blocks > (ref 0) > /bin/false contains 11 bytes in 1 > blocks (ref 0) > /dev/null contains 10 bytes in 1 > blocks (ref 0) > System User contains 12 bytes in 1 > blocks (ref 0) > x contains 2 bytes in 1 > blocks (ref 0) > IUSR_JUNIPER contains 13 bytes in 1 > blocks (ref 0) > > There's 4689 copies of this, and it seems to increase roughly in proportion > to smbd's memory use. Ie. There were 2xxx copies ealier today when it was > using half the memory.
Are all the copies identical? Can you remind me some details about your setup? What is "IUSR_UNIIPER"? Given this output, I'm presuming we have a call to talloc_getpwnam() that is not talloc_free()'ing the result. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. http://redhat.com
signature.asc
Description: This is a digitally signed message part
