Bug#407517: [Pkg-samba-maint] Bug#407517: weekly Samba/ldapsamfailureserving files to a busy win2k client

[Jamie ffolliott]

> > > 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"?

Yeah it appears they are all identical, I sent a copy of the pool-usage
output in the last email if you want to have a look.

IUSR_JUNIPER is a domain user on "JUNIPER" that executes within the IIS5.0
webserver and accesses the "web" fileshare on KINGWOOD where samba is
running.  There's about 60 processes executing as IUSR_JUNIPER, and roughly
60 smb connections to kingwood.  Each of those processes run an ihtml
application server as an ISAPI dll (much like asp or php) which will open
additional files on the "web" fileshare.

Kingwood is debian/linux testing, with kernel 2.4.27, samba is a PDC, and
it's also doing some filesharing for a few win2k clients running IIS
webservers.

Juniper is Win2k SP4, and is a member of the domain.

> > Given this output, I'm presuming we have a call to 
> talloc_getpwnam() 
> > that is not talloc_free()'ing the result.
> 
> Actually, the call would be getpwnam_alloc().  Anyway, can I 
> get some more context around that output?  I'm interested in 
> the parent information, and any other details you can give me.

If there's any other info you need, let me know.

Jamie