[Samba] Samba 3.0.23c memory usage increased ten fold to over 70Mb / smbd process

[Duncan Brannen]

Hi,
   I'm running samba 3.0.23c on Solaris 10.  The smbd processes on my PDC
have increased in size from 7Mb to upto  86 Mb , the majority of which 
seems to
be resident .

  3940 root       77M   72M sleep   59    0   0:00:01 0.1% smbd/1
 14174 root       77M   73M sleep   59    0   0:00:10 0.1% smbd/1
 13551 root       77M   73M sleep   59    0   0:00:18 0.1% smbd/1
 19888 root       77M   73M sleep   59    0   0:00:10 0.1% smbd/1
 29251 root       77M   73M sleep   59    0   0:00:13 0.1% smbd/1
 20490 root       78M   73M sleep   59    0   0:00:19 0.1% smbd/1
  1311 root       86M   81M sleep   59    0   0:05:58 0.1% smbd/1
  7095 root       77M   70M sleep   59    0   0:00:00 0.0% smbd/1
  1969 root       77M   73M sleep   59    0   0:00:02 0.0% smbd/1
 10797 root       84M   79M sleep   59    0   0:06:06 0.0% smbd/1
  7638 root       74M   49M sleep   59    0   0:00:00 0.0% smbd/1
 29414 root       77M   71M sleep   59    0   0:00:00 0.0% smbd/1
 28282 root       79M   74M sleep   59    0   0:00:40 0.0% smbd/1
  3155 root       77M   72M sleep   59    0   0:00:01 0.0% smbd/1
 21683 root       77M   70M sleep   59    0   0:00:06 0.0% smbd/1
  2996 root       77M   71M sleep   59    0   0:00:01 0.0% smbd/1

The increase seems to be coming from the connections.tdb file which is 
being loaded
by every process

 From pmap

FA400000   64896K rw-s-  dev:32,0 ino:301744

the address changes for each smbd process but the dev:32,0 ino:301744 
remains constant

-rw-r--r--   1 root     root     66453504 Sep 29 15:07 
/usr/local/samba/var/locks/connections.tdb

(Sizes are identical, so I guess it's this file which is mapped)

I've currently got 480 smbd processes running and very little RAM left.


Question : Can I clean out the connections.tdb somehow or is it a case 
of shutdown / close all user files
and delete connections.tdb / restart?

Our classrooms are 24 hour so restarting is difficult.

Is setting Max Connections to 1 on the net logon share a viable way to 
stop Win2K machines getting that
server as their %LOGONSERVER% and thus getting users off to let me 
restart (We've 3 BDC's doing nothing)

Our clients are on Networks A,B,C,D,E and F

we have a PDC on Z, BDC's on W,X and Y

Wins-server on G

Is there a way to bias the Win2K clients towards the BDCs?  I've 
currently got approx 15 connectinos to each BDC
and 480 to the PDC, they're in similar areas & ping times to each are 
equivalent. That would get some of the
memory load off the PDC.


Cheers,
       Duncan