tdb/tdb.c: tdb_oob() significance (when not using MMAP)

Volker Lendecke Volker.Lendecke at SerNet.DE
Tue Oct 17 20:06:10 GMT 2006

On Tue, Oct 17, 2006 at 05:18:12PM +0530, dhruva wrote:
> On VMS port, we are finding some cases where the call to stat returns
> a size smaller than the total lenght (file pointer offset + size of
> data to be written). I initially thought of calling ftruncate() to
> increase the file size in tdb_oob() which worked. I have a basic doubt
> on the relevance of tdb_oob() when not using MMAP.

Looking at the places where tdb->map_size is used I get the
impression that tdb_free() would not correctly coalesce free
records if map_size is not updated correctly, even without
mmap() around.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :

More information about the samba-technical mailing list