samba.git/source3/lib/id_cache.c, branch talloc-2.3.2

lib/util: move memcache.[ch] to the toplevel 'samba-util' library

2014-07-18T13:43:33+00:00

This is generic enough that it could be used in all code.

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Volker Lendecke 

Autobuild-User(master): Stefan Metzmacher 
Autobuild-Date(master): Fri Jul 18 15:43:33 CEST 2014 on sn-devel-104

s3:id_cache: do not use the in-memory idmap cache (it is going to be removed)

2012-04-20T21:17:36+00:00

This also removes the ID_CACHE_FLUSH message.

s3:smbcontrol: let smbd pass the idmap msg to its children for convenience

2011-10-12T20:45:53+00:00

Signed-off-by: Michael Adam

s3: fix id_cache_kill to delete the the id-mappig from caches

2011-10-12T20:45:52+00:00

The intendet and documented behavior of smbcontrol smbd idmap kill is to
delete the mapping from caches and additionally kill the smbd if an affected id
is in use.

Signed-off-by: Michael Adam

s3-passdb: Keep caches coherent

2011-08-21T13:08:25+00:00

When deleting a user send a message to all interested parties so they can
purge their caches. Otherwise some processes may positively respond with a
cached getpwnam, when the user have actully been removed.

Without this some tests that remove and then immediately create users are
flakey.

Signed-off-by: Simo Sorce

s3-id_cache: Use better names for id cache management ops

2011-08-21T13:08:25+00:00

The IDMAP term is normally associated with Winbind's idmap stuff.
These functions deal with id caching not id mapping.

Signed-off-by: Simo Sorce

s3-id_cache: Move id caches mgmt out of smbd

2011-08-21T13:08:25+00:00

We must leave the MSG_IDMAP_KILL operation in SMBD as it uses smbd
specific internal globals and makes sense only in the context of a smbd
daemon.
The rest is moved under lib/ as we need to deal with id cache cleanups
in other daemons too (like lsasd).

Signed-off-by: Simo Sorce