unsubscribe

[Mark Green]

-----Original Message-----
From: Agent Drek [mailto:drek at bigstudios.com]
Sent: Tuesday, September 12, 2000 6:54 AM
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?
> 
> 

ok I've got more info now :)

PID STAT      TIME  SL  RE PAGEIN   VSZ  RSS   LIM TSIZ %CPU %MEM COMMAND
274 I      0:11.22  24 641     15 20008 18196     -  324  0.0 14.2
/opt/samba-tng/sbin/smbd -D
304 I      0:04.33  21 324      2 14288 12636     -  324  0.0  9.9
/opt/samba-tng/sbin/smbd -D
278 S      0:00.03   4 625      5  4604 2636     -  324  0.0  2.1
/opt/samba-tng/sbin/smbd -D
334 I      0:00.02  20  81      1  4608 2564     -  324  0.0  2.0
/opt/samba-tng/sbin/smbd -D
280 I      0:00.03  25 510      0  4608 2340     -  324  0.0  1.8
/opt/samba-tng/sbin/smbd -D
336 S      0:00.02  13  73      2  4608 2604     -  324  0.0  2.0
/opt/samba-tng/sbin/smbd -D
200 Is     0:00.01  73 726      0  3240 1660     -  324  0.0  1.3
/opt/samba-tng/sbin/smbd -D

where RSS is the 'resident set size' TSIZ is the 'text size Kb' VSZ 'virtual
size in Kb'

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?

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!

just to reiterate that this is occuring on FreeBSD4.1-Release with a recent
version of samba-tng (obtained through cvs).

thanks,

--
    Agent Drek

Big Animation Inc > 'digital plumber'
http://www.bigstudios.com