s3:idmap_tdb2: remove use of idmap_tdb2_state from idmap_tdb2_allocate_id
authorMichael Adam <obnox@samba.org>
Wed, 16 Jun 2010 13:31:55 +0000 (15:31 +0200)
committerMichael Adam <obnox@samba.org>
Sat, 14 Aug 2010 00:10:43 +0000 (02:10 +0200)
commit834008c2cd55a87d4fada2390606381ec7316915
tree29fdebeb9c4beb47ce65d53ee5e0ef6d4fe214d8
parent1dfb20d0292623f21f47e93afaba865d9ff3b05b
s3:idmap_tdb2: remove use of idmap_tdb2_state from idmap_tdb2_allocate_id

idmap_tdb2_state should actually be called idmap_tdb2_alloc_context.
This is being removed as the idmap and allocation is moved together.
We use the idmap_tdb2_context * that is sitting in dom->private_data.
This contains the same ranges as those in the state anyways.
Later, when we can also allocate for named domains, this will become
necessary anyways.
source3/winbindd/idmap_tdb2.c