rpcrt4: Fix a comment and move a WARN to where it really indicates a problem, rather than falsely triggering on normal conditions.
This commit is contained in:
parent
7a1522a20f
commit
59a90143bf
|
@ -115,16 +115,16 @@ static RPC_STATUS rpcrt4_conn_listen_pipe(RpcConnection_np *npc)
|
|||
if (ConnectNamedPipe(npc->pipe, &npc->ovl))
|
||||
return RPC_S_OK;
|
||||
|
||||
WARN("Couldn't ConnectNamedPipe (error was %d)\n", GetLastError());
|
||||
if (GetLastError() == ERROR_PIPE_CONNECTED) {
|
||||
SetEvent(npc->ovl.hEvent);
|
||||
return RPC_S_OK;
|
||||
}
|
||||
if (GetLastError() == ERROR_IO_PENDING) {
|
||||
/* FIXME: looks like we need to GetOverlappedResult here? */
|
||||
/* will be completed in rpcrt4_protseq_np_wait_for_new_connection */
|
||||
return RPC_S_OK;
|
||||
}
|
||||
npc->listening = FALSE;
|
||||
WARN("Couldn't ConnectNamedPipe (error was %d)\n", GetLastError());
|
||||
return RPC_S_OUT_OF_RESOURCES;
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue