From 6cbf3ecd6669f73d9a1b64118956b49439de74bc Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Mon, 5 May 2014 16:27:59 +1200 Subject: s4:pyrpc: explicitly use dcerpc_binding_handle_set_sync_ev() for irpc This indicates that we may use nested event loops... Andrew Bartlett Pair-Programmed-With: Stefan Metzmacher Change-Id: Id014dcc68699c86cb99015a91a6979e30795f727 Signed-off-by: Andrew Bartlett Signed-off-by: Stefan Metzmacher --- source4/librpc/rpc/pyrpc_util.c | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'source4/librpc') diff --git a/source4/librpc/rpc/pyrpc_util.c b/source4/librpc/rpc/pyrpc_util.c index 314ad2cc8d7..226c884d3ef 100644 --- a/source4/librpc/rpc/pyrpc_util.c +++ b/source4/librpc/rpc/pyrpc_util.c @@ -83,6 +83,12 @@ static NTSTATUS pyrpc_irpc_connect(TALLOC_CTX *mem_ctx, const char *irpc_server, return NT_STATUS_INVALID_PIPE_STATE; } + /* + * Note: this allows nested event loops to happen, + * but as there's no top level event loop it's not that critical. + */ + dcerpc_binding_handle_set_sync_ev(*binding_handle, event_ctx); + return NT_STATUS_OK; } -- cgit