samba.git/lib/tdb_compat, branch master

ccan: we're subsystems, not a library.

2012-06-29T04:22:44+00:00

Don't expose a libccan.so; it would produce clashes if someone else
does the same thing.  Unfortunately, if we just change it from a
SAMBA_LIBRARY to a SAMBA_SUBSYSTEM, it doesn't create a static library
as we'd like, but links all the object files in.  This means we get
many duplicates (eg. everyone gets a copy of tally, even though only
ntdb wants it).

So, the solution is twofold:
1) Make the ccan modules separate.
2) Make the ccan modules SAMBA_SUBSYSTEMs not SAMBA_LIBRARYs so we don't
   build shared libraries which we can't share.
3) Make the places which uses ccan explicit.

Signed-off-by: Rusty Russell 

Autobuild-User(master): Rusty Russell 
Autobuild-Date(master): Fri Jun 29 06:22:44 CEST 2012 on sn-devel-104

TDB2: make SAMBA use tdb1 again for the moment.

2012-06-19T03:38:05+00:00

Otherwise the following surgery will break the SAMBA build and testsuite.

Signed-off-by: Rusty Russell

tdb-compat: Add tdb_chainlock_nonblock

2012-04-17T08:20:59+00:00

lib/tdb_compat: Do not define BUILD_TDB2 if we are not building tdb2

2012-04-11T14:00:38+00:00

The simple fact that this was defined at all, even to false, caused some
of the tdb2 build code to run.

Andrew Bartlett

tdb_compat: only use hashsize attribute when O_CREAT

2012-01-29T23:36:55+00:00

tdb2 complains if you specify a tdb1 hashsize, and you're not actually
trying to create a new database.

Signed-off-by: Rusty Russell

tdb_compat: add "TDB_COMPAT_USE_TDB2" environment variable

2011-09-21T03:28:59+00:00

When BUILD_TDB2 is defined, add TDB_VERSION1 flag to all tdb_open()
calls, unless this flag is set.  This means we use the tdb1 on-disk
format unless the user specifically asks for tdb2.

We'd love to do this using loadparm, but we need to work with both
Samba 3 and Samba 4's loadparm, and they're not unified yet.

Signed-off-by: Rusty Russell

tdb_compat: honour hashsize arg when using tdb2 with TDB_VERSION1 flag.

2011-09-21T03:27:59+00:00

We use the TDB_ATTRIBUTE_TDB1_HASHSIZE to set the hash size.

Signed-off-by: Rusty Russell

tdb_compat: handle TDB_VOLATILE flag.

2011-09-21T03:26:59+00:00

This is only meaningful when using the TDB_VERSION1 flag: we set the
attribute to control the maximum number of dead records (to 5, which is
what TDB_VOLATILE did for tdb1).

Signed-off-by: Rusty Russell

tdb_compat: handle TDB_INCOMPATIBLE_HASH flag.

2011-09-21T03:25:59+00:00

This is only meaningful when using the TDB_VERSION1 flag: it is done
by using a magic hash value (which will fall back to the default hash
if that works instead).

Signed-off-by: Rusty Russell

tdb_compat: change offset of CLEAR_IF_FIRST lock.

2011-09-14T00:21:29+00:00

This makes it match tdb1, which mean it will Just Work as TDB2 gets
tdb1 format support.

Signed-off-by: Rusty Russell 

Autobuild-User: Rusty Russell 
Autobuild-Date: Wed Sep 14 02:21:29 CEST 2011 on sn-devel-104