Fix winbindd not to sit in a busy loop...

Clearly winbindd in Samba4 has not ever been run against windows, as
when we fixed the Samba4 server not to cause XP to loop like this,
Samba4's own client starts looping...

Andrew Bartlett
(This used to be commit 9741772190a85c7c42c17ff24a4aa3f53fbc9f3a)

diff --git a/source4/winbind/wb_cmd_list_trustdom.c b/source4/winbind/wb_cmd_list_trustdom.c
index 8d0c1bd947c17eff426f5cf5ed69b6fe7e74433f..fe98ce2f6a1a9dd637ea9d9703c8764358975fee 100644 (file)
--- a/source4/winbind/wb_cmd_list_trustdom.c
+++ b/source4/winbind/wb_cmd_list_trustdom.c
@@ -159,7 +159,8 @@ static void cmd_list_trustdoms_recv_doms(struct rpc_request *req)
                        state->r.out.domains->domains[i].sid);
        }
 
-       if (NT_STATUS_IS_OK(state->ctx->status)) {
+       if (NT_STATUS_IS_OK(state->ctx->status) || NT_STATUS_EQUAL(state->ctx->status, NT_STATUS_NO_MORE_ENTRIES)) {
+               state->ctx->status = NT_STATUS_OK;
                composite_done(state->ctx);
                return;
        }