samba.git/lib/ntdb, branch talloc-2.0.8

pyntdb: Fix init function for ntdb python module.

2012-09-25T20:40:39+00:00

Signed-Off-By: Jelmer Vernooij 

Autobuild-User(master): Jelmer Vernooij 
Autobuild-Date(master): Tue Sep 25 22:40:39 CEST 2012 on sn-devel-104

ntdb: Try to fix the build on Solaris which does not have err

2012-09-23T04:31:01+00:00

lib/ntdb: Fix format string errors found by -Werror=format in ntdb tests

2012-07-30T04:25:10+00:00

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

ntdb: take advantage of direct access across expand.

2012-06-22T05:35:17+00:00

This means we no longer have to unmap if we want to compare a record.

Signed-off-by: Rusty Russell

ntdb: test arbitrary operations during ntdb_parse_record().

2012-06-22T05:35:17+00:00

In particular, this tests that we can store enough records to make the
database expand while we map the given record.  We use a global lock for
this, but it could happen in theory with another process.

It also tests the that we can recurse inside ntdb_parse_record().

Signed-off-by: Rusty Russell

ntdb: make database read-only during ntdb_parse() callback.

2012-06-22T05:35:17+00:00

Since we have a readlock, any write will grab a write lock: if it happens
to be on the same bucket, we'll fail.

For that reason, enforce read-only so every write operation fails
(even for NTDB_NOLOCK or NTDB_INTERNAL dbs), and document it!

Signed-off-by: Rusty Russell

ntdb: allow direct access for NTDB_INTERNAL dbs during expansion.

2012-06-22T05:35:17+00:00

NTDB_INTERNAL databases need to malloc and copy to keep old versions
around if we expand, in a similar way to the manner in which keep old
mmaps around.

Of course, it only works for read-only accesses, since the two copies
are not synced.

Signed-off-by: Rusty Russell

ntdb: enhancement to allow direct access to the ntdb map during expansion.

2012-06-22T05:35:17+00:00

This means keeping the old mmap around when we expand the database.
We could revert to read/write, except for platforms with incoherent
mmap (ie. OpenBSD), where we need to use mmap for all accesses.

Thus we keep a linked list of old maps, and unmap them when the last access
finally goes away.

This is required if we want ntdb_parse_record() callbacks to be able
to expand the database.

Signed-off-by: Rusty Russell

ntdb: don't munmap the database on every close.

2012-06-22T05:35:17+00:00

Since we can have multiple openers, we should leave the mmap in place
for the other openers to use.  Enhance the test to check the bug (it
still works, because without mmap we fall back to read/write, but
performance would be terrible!).

Signed-off-by: Rusty Russell