TDB on OpenBSD problem.

[Jason Coene]

Jeremy,

It is not starting at such a high number. The log files overflow
(and log.smbd.old is created, then its replaced by another old, etc. etc.)
before i can stop the smbd process (and children). I always delete the
/var/spool/lock/* files (thats where my tdb files go), and the log files
before testing a new build.

I do have some more information about the error.

It seems to happen when two computers connect. A Typical Scenario:

1) computer JASON WIN2K (not domain member) connects to server ESKIMO.
   Reads lots of files, everything works great.
2) computer BILLY NT40W (not domain member) connects to server ESKIMO.
   Before eskimo gives a share listing, it spits all the TDB information.
3) smbd forks multiple times, and when killing the parent PID,
   the children do NOT die immediately. It takes multiple kill -9's to the
   children to fix the error.

I tried capping the size (if tdb->max_size >= MAX_SIZE_I_DECLARE)
return -1 in tdb_expand, it worked. Clients can connect, until
it starts logging "no more connections allowed". After 2 pc's connect
to 3 shares each, the max. connections are used. The MAX_SIZE_I_DECLARE
was around 1600KB. The PC # and share # are very rough, i only tried this
in a few diff. scenarios. 6 seems to be the magic number of shares, though,
not including 1 connect to each pc.

tdb_expand runs nicely a few times, all expanding to 8192 until it goes
berzerk.

I tried looking at tdb_allocate. It seems to be the only function that calls
tdb_expand, and tdb_store seems to be the only function to call
tdb_allocate.
Am i correct in this assumption?

Regards,

Jason Coene

###  -----Original Message-----
###  From: samba-technical-admin at lists.samba.org
###  [mailto:samba-technical-admin at lists.samba.org]On Behalf Of Jeremy
###  Allison
###  Sent: Wednesday, May 02, 2001 3:07 PM
###  To: Jason Coene
###  Cc: Simo Sorce; tridge at valinux.com; samba-technical at samba.org
###  Subject: Re: TDB on OpenBSD problem.
###
###
###  Jason Coene wrote:
###  >
###  > Simo,
###  >
###  > I am completely new to the TDB system, but am i to assume
###  that map_ptr is
###  > the
###  > "target size"? If so, its very fond of my hard drives :]
###  >
###  > Samba did this when i went run:\\eskimo in windows explorer :o
###  >
###  >   PRE-TDB_ALIGN:  map_size: 475447296, map_ptr: 1075863552, size: 620
###  >   POST-TDB_ALIGN: map_size: 475447296, map_ptr: 1075863552,
###  size: 8192
###  >   LSEEK VALUE: 475455487
###
###  No, map_size is the target size, map_ptr is just the
###  address it's being mapped at.
###
###  If your map_size is *starting* at 475447296, then something
###  is broken to begin with.
###
###  Ensure that the connection tdb is deleted before starting
###  smbd and send in these logs again please.
###
###  Jeremy.
###
###  --
###  --------------------------------------------------------
###  Buying an operating system without source is like buying
###  a self-assembly Space Shuttle with no instructions.
###  --------------------------------------------------------
###
###