From 2bbc91978b7d0b18191acb650a96f5e39d538c1c Mon Sep 17 00:00:00 2001 From: Andrew Tridgell Date: Mon, 10 Dec 2001 06:05:21 +0000 Subject: winbindd backends can now be marked "consistent" or "inconsistent" consistent backends (like ADS) always give correct primary group info, so we can play cache tricks to speed things up a lot inconsistent backends (like MSRPC) need to fetch stuff more often (This used to be commit 217c39f23282e20f96a61a0d5a2434b3f5f66a86) --- source3/nsswitch/winbindd.h | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'source3/nsswitch/winbindd.h') diff --git a/source3/nsswitch/winbindd.h b/source3/nsswitch/winbindd.h index 26181326bb..e22824f33c 100644 --- a/source3/nsswitch/winbindd.h +++ b/source3/nsswitch/winbindd.h @@ -85,10 +85,12 @@ typedef struct { } WINBIND_USERINFO; /* per-domain methods. This is how LDAP vs RPC is selected - This will eventually be the sole entry point to all the methods, - I'm just starting small */ struct winbindd_methods { + /* does this backend provide a consistent view of the data? (ie. is the primary group + always correct) */ + BOOL consistent; + /* get a list of users, returning a WINBIND_USERINFO for each one */ NTSTATUS (*query_user_list)(struct winbindd_domain *domain, TALLOC_CTX *mem_ctx, -- cgit