memory hungry smbd in samba-tng?

[Cole, Timothy D.]

> -----Original Message-----
> From:	Agent Drek [SMTP:drek at bigstudios.com]
> Sent:	Tuesday, September 12, 2000 9:54
> To:	Cole, Timothy D.
> Cc:	samba-ntdom at samba.org; drek at bigstudios.com
> Subject:	RE: memory hungry smbd in samba-tng?
> 
> On Fri, 1 Sep 2000, Cole, Timothy D. wrote:
> 
> > 	Hrm, this is a general problem, then... be interesting to see where
> > the memory is going.  How much is text, and how much is data?
> 
> I've also found that if I launch smbd from a csh script with
> 'limit datasize 20M' it will crash. I think that it may have something to
> do with the name mangling cache as the following log message does not make
> sense to me:
> 
> name_map_mangle( minfo.exe, need83 = FALSE, cache83 = TRUE, 6 )
> 
> samba decides that each opened file does not need name mangling and then
> goes ahead and sets cache83 = TRUE ... is that logical?
> 
	Depends on how the name mangling stuff is implemented, really.
Maybe the name is still required in the cache to prevent collisions when
other names are mangled... although, it'd need to avoid collisions with
previously unaccessed filenames too (meaning it needs to rescan the
directory), so that probably doesn't really buy much.

	This may not be the culprit, but it might be worth
re-examining/fixing anyway.

> I read though all the current bug/patch submissions and nothing seemed to
> point here ... I tried turning off name mangling but I could still crash
> the system and now people have arrived at work ( I have a ~1hr window to
> work with in the morning).
> 
> does it sound like I'm chasing a ghost? csh suggestion came from someone
> on freebsd-questions who thought I should do a crash dump (trace) of smbd
> which is what I guess I'll do tommorow morning but this is definately
> getting complicated!
> 
	These things invariably are.  I'm not really sure how much good a
crash dump will do in this case, though, except perhaps to examine in-core
data structures (which you could presumably do anyway by attaching a
debugger).

	Keep in mind that the code that puts you over the top is not
necessarily going to be the code that got you most of the way there.
(although it is still worth a try to see where it ends up)