summaryrefslogtreecommitdiff
path: root/src/providers/ldap/sdap_async_enum.c
diff options
context:
space:
mode:
authorJakub Hrozek <jhrozek@redhat.com>2013-09-11 16:57:30 +0200
committerJakub Hrozek <jhrozek@redhat.com>2013-09-11 19:42:53 +0200
commitfc6afb011198f84a30e6598c62923b5a588ccd54 (patch)
tree6b77c58c6117657e6c01703c709740dba67cbb18 /src/providers/ldap/sdap_async_enum.c
parent114c1ed8ec72b43f04527b4f3b4f0940c1fb2c54 (diff)
downloadsssd-fc6afb011198f84a30e6598c62923b5a588ccd54.tar.gz
sssd-fc6afb011198f84a30e6598c62923b5a588ccd54.tar.bz2
sssd-fc6afb011198f84a30e6598c62923b5a588ccd54.zip
LDAP: Store cleanup timestamp after initial cleanup
When the SSSD changes serves (and hence lastUSN) we perform a cleanup as well. However, after recent changes, we didn't set the cleanup timestamp correctly, which made the lastUSN logic fail.
Diffstat (limited to 'src/providers/ldap/sdap_async_enum.c')
-rw-r--r--src/providers/ldap/sdap_async_enum.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/providers/ldap/sdap_async_enum.c b/src/providers/ldap/sdap_async_enum.c
index 625db645..9a520ba5 100644
--- a/src/providers/ldap/sdap_async_enum.c
+++ b/src/providers/ldap/sdap_async_enum.c
@@ -311,7 +311,7 @@ static void sdap_dom_enum_services_done(struct tevent_req *subreq)
}
if (state->purge) {
- ret = ldap_id_cleanup(state->ctx->opts, state->sdom->dom);
+ ret = ldap_id_cleanup(state->ctx->opts, state->sdom);
if (ret != EOK) {
/* Not fatal, worst case we'll have stale entries that would be
* removed on a subsequent online lookup