summaryrefslogtreecommitdiff
path: root/source3/lib/id_cache.c
AgeCommit message (Collapse)AuthorFilesLines
2011-10-12s3:smbcontrol: let smbd pass the idmap msg to its children for convenienceGregor Beck1-12/+12
Signed-off-by: Michael Adam <obnox@samba.org>
2011-10-12s3: fix id_cache_kill to delete the the id-mappig from cachesGregor Beck1-2/+2
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 <obnox@samba.org>
2011-08-21s3-passdb: Keep caches coherentAndreas Schneider1-0/+15
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 <idra@samba.org>
2011-08-21s3-id_cache: Use better names for id cache management opsAndreas Schneider1-13/+13
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 <idra@samba.org>
2011-08-21s3-id_cache: Move id caches mgmt out of smbdAndreas Schneider1-0/+190
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 <idra@samba.org>