summaryrefslogtreecommitdiffstats
path: root/source3/winbindd/idmap_tdb2.c
Commit message (Collapse)AuthorAgeFilesLines
* s3:idmap_tdb2: fix bug 8368 : correctly initialize "idmap config * : script" ↵Michael Adam2011-08-101-1/+1
| | | | | | | | | with NULL this fixes the fallback to the deprecated spelling idmap:script Autobuild-User: Michael Adam <obnox@samba.org> Autobuild-Date: Wed Aug 10 14:59:32 CEST 2011 on sn-devel-104
* s3:dbwrap: move all .c and .h files of dbwrap to lib/dbwrap/Michael Adam2011-07-291-1/+1
| | | | | Autobuild-User: Michael Adam <obnox@samba.org> Autobuild-Date: Fri Jul 29 13:34:22 CEST 2011 on sn-devel-104
* s3:dbwrap: move db_open() to a file dbwrap_open.c of its own.Michael Adam2011-07-291-0/+1
| | | | | | Also start new folder lib/dbwrap/ where dbwrap_open.c is stored and make the fallbacke implementation functoins non-static and create a dbwrap_private.h header file that contains their prototypes.
* s3:idmap_tdb2: remove the undocumented option of the silly name "tdb:idmap2.tdb"Michael Adam2011-07-271-5/+1
| | | | | | | | | | | | | | | In ancient times, when ctdb had not support for persistent databases and tdb2 was introduced as a two-layer solution and it was more important than today to be able to change the location of the permanent database file because it had to reside on shared storage. But these were times when idmap_tdb2 was not even officially released. Nowadays, with ctdb handling the persistent idmap2.tdb database, the path is stripped anyways, so this undocumented option has become unnecessary and is hence removed. Autobuild-User: Michael Adam <obnox@samba.org> Autobuild-Date: Wed Jul 27 05:37:57 CEST 2011 on sn-devel-104
* s3:idmap_tdb2: remove a legacy commentMichael Adam2011-07-271-1/+0
|
* s3:idmap_tdb2: remove legacy commentMichael Adam2011-07-271-2/+0
|
* s3:idmap_tdb2: remove superfluous initialization with bogus commentMichael Adam2011-07-271-3/+0
|
* s3:idmap_tdb2: fix a legacy comment that does not apply any moreMichael Adam2011-07-271-2/+1
|
* s3:idmap_tdb2: deprecate the idmap:script parameter and use "idmap config * ↵Michael Adam2011-07-271-18/+21
| | | | | | | | | : script" instead With this patch, "idmap config * : script" will override "idmap : script". If "idmap : script" is present, a deprecation warning will be printed in any case. If "idmap config * : script" is not set, then the value of "idmap :script" will be used for backwards compatibility.
* s3: only include tdb headers where needed.Günther Deschner2011-05-061-0/+1
| | | | Guenther
* s3:idmap_tdb2: fix build of tdb2Michael Adam2011-04-041-0/+1
| | | | The include of system/filesys.h was removed from includes.h. ...
* s3:idmap: remove the params argument from the init functionMichael Adam2011-03-221-2/+1
|
* s3: Enhance error messages in idmap_tdb2_init_hwmVolker Lendecke2011-03-131-8/+9
| | | | | Autobuild-User: Volker Lendecke <vlendec@samba.org> Autobuild-Date: Sun Mar 13 12:59:37 CET 2011 on sn-devel-104
* s3-idmap: fix the build of idmap_tdb2.Günther Deschner2011-03-081-11/+1
| | | | | | | Guenther Autobuild-User: Günther Deschner <gd@samba.org> Autobuild-Date: Tue Mar 8 10:51:04 CET 2011 on sn-devel-104
* s3: fix the build of idmap_adex, idmap_tdb2, idmap_hash and several vfs modules.Günther Deschner2010-10-181-0/+1
| | | | | | | Guenther Autobuild-User: Günther Deschner <gd@samba.org> Autobuild-Date: Mon Oct 18 14:39:39 UTC 2010 on sn-devel-104
* s3-build: use dbwrap.h only where needed.Günther Deschner2010-08-261-0/+1
| | | | Guenther
* s3-idmap: only include idmap headers where needed.Günther Deschner2010-08-261-0/+1
| | | | Guenther
* s3:idmap_tdb2: use idmap_rw_new_mapping in idmap_tdb2_new_mappingMichael Adam2010-08-141-34/+6
|
* s3:idmap_tdb2: add rw_ops to idmap_tdb2_context and initialize in ↵Michael Adam2010-08-141-0/+12
| | | | idmap_tdb2_db_init
* s3:idmap_tdb2: add my (C)Michael Adam2010-08-141-0/+1
|
* s3:idmap_tdb2: move idmap_tdb2_new_mapping() up. spare a prototype.Michael Adam2010-08-141-55/+51
|
* s3:idmap_tdb2: get rid of an extra variable in idmap_tdb2_db_init().Michael Adam2010-08-141-1/+0
|
* s3:idmap_tdb2: move idmap_tdb2_set_mapping() up to its _action callback.Michael Adam2010-08-141-61/+62
|
* s3:idmap_tdb2: use the right talloc context for db_open in idmap_tdb2_open_db()Michael Adam2010-08-141-1/+1
|
* s3:idmap_tdb2: don't check whether sid is already mapped in ↵Michael Adam2010-08-141-22/+0
| | | | | | | | idmap_tdb2_new_mapping(). idmap_tdb2_new_mapping() is called from inside a transaction only with sids, that have been verified not to be mapped directly before that in the same transaction.
* s3:idmap_tdb2: add the db_context to the idmap_tdb2_contextMichael Adam2010-08-141-19/+32
| | | | this removes the idmap_tdb2 global variable
* s3:idmap_tdb2: talloc_zero (instead of talloc) the idmap_tdb2_contextMichael Adam2010-08-141-1/+1
|
* s3:idmap_tdb2: rename idmap_tdb2_alloc_load -> idmap_tdb2_init_hwmMichael Adam2010-08-141-5/+4
|
* s3:idmap_tdb2: move idmap_tdb2_alloc_load() up to reduce need for prototypeMichael Adam2010-08-141-36/+35
|
* s3:idmap_tdb2: remove unused idmap_tdb2_state and idmap_tdb2_load_rangesMichael Adam2010-08-141-51/+0
|
* s3:idmap_tdb2: give idmap_tdb2_alloc_load() and idmap domain arguemntMichael Adam2010-08-141-7/+7
| | | | and use the ranges from the idmap domain for checking the HWM values
* s3:idmap_tdb2: add an idmap_domain struct argument to idmap_tdb2_open_db()Michael Adam2010-08-141-9/+9
|
* s3:idmap_tdb2: remove filter_low_id and filter_high_id from idmap_tdb2_contextMichael Adam2010-08-141-2/+0
| | | | Now these are taken from the idmap_domain struct.
* s3:idmap_tdb2: don't parse config and fill filter_low_id and filter_high_idMichael Adam2010-08-141-43/+1
| | | | | into idmap_tdb2_context in idmap_tdb2_db_init(). Now these are taken from the idmap_domain struct instead.
* s3:idmap_tdb2: honour the "idmap read only" flag in the tdb2 module.Michael Adam2010-08-141-1/+1
| | | | | | Note that this will not prevent the idmap script from writing its mappings to the database, but no new unix ids will be allocated via the allocator and hence no new mappings will be autogenerated.
* s3:idmap_tdb2: use range from idmap_domain in idmap_tdb2_allocate_idMichael Adam2010-08-141-4/+1
|
* s3:idmap_tdb2: use filter from idmap_domain rather than from idmap_tdb2_contextMichael Adam2010-08-141-12/+6
|
* s3:idmap_tdb2: pass idmap_domain (not idmap_tdb2_context) to ↵Michael Adam2010-08-141-7/+5
| | | | idmap_tdb2_sid_to_id
* s3:idmap_tdb2: pass idmap_domain instead of idmap_tdb2_context to ↵Michael Adam2010-08-141-6/+7
| | | | | | | idmap_tdb2_unixids_to_sids The reason for this will become apparent later: The ranges are being moved to the idmap_domain: They are universal.
* s3:idmap_tdb2: also support idmap script for named domainsMichael Adam2010-08-141-0/+5
| | | | this can be configured via "idmap config DOMAIN : script = foobar"
* s3:idmap_tdb2: move the idmap script from idmap_tdb2_state to idmap_tdb2_contextMichael Adam2010-08-141-15/+11
| | | | | | The state (aka idmap_tdb2_alloc_context) is being removed. The (global) idmap script was wrong there anyways. It belongs to the per-domain context.
* s3:idmap_tdb2: remove use of idmap_tdb2_state from idmap_tdb2_allocate_idMichael Adam2010-08-141-4/+8
| | | | | | | | | 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.
* s3:idmap_tdb2: move definition of struct idmap_tdb2_context up.Michael Adam2010-08-141-4/+5
|
* s3:idmap_tdb2: open the db after loading the ranges in idmap_tdb2_db_init().Michael Adam2010-08-141-3/+5
|
* s3:idmap_tdb2: add allocation of new mappings to idmap_tdb2_sids_to_unixidsMichael Adam2010-08-141-22/+173
| | | | | | | | | | | This moves the new_mapping feature inside the tdb2 backend to make creations of mappings atomic. Note: The new internal function idmap_tdb2_get_new_id() that is used to allocate a new unix id is prepared to function for multiple explicitly configured idmap domains, but currently it does only work for the default domain. The extended allocation support requires extension of the data base format to store multiple counters (per domain). This will be added in a later step (TODO!).
* s3:idmap_tdb2: re-implement allocated_id in idmap methods.Michael Adam2010-08-141-0/+1
|
* s3:idmap_tdb2: remove unused idmap_tdb2_alloc_init().Michael Adam2010-08-141-12/+0
|
* s3:idmap_tdb2: remove unused idmap_tdb2_alloc_close().Michael Adam2010-08-141-9/+0
|
* s3:idmap_tdb2: remove unused idmap_alloc_methods.Michael Adam2010-08-141-6/+0
|
* s3:idmap_tdb2: don't call smb_register_idmap_alloc() in idmap_tdb2_initMichael Adam2010-08-141-9/+0
| | | | | | The registering of alloc backends is being removed. The idmap backends are responsible for initializing their alloc code on their own if necessary.