Use g_debug instead of g_warning in RpcChannel_Error

With esx5.1GA Tools, when there are more two Terminal Sessions
connect to a Windows VM, each TS sould have one vmtoolsd running
but actually only max two vmtoolsd run.  The Windowds Application
Event log fills up with the warning messages of
	"[vmusr:vmusr] Error in the RPC receive loop: RpcIn: Unable to send."
repeatly until close some TS' to have max two TS connected. Some
customers had vmtoolsd crashed but some didn't.  This message is from
RpcChannel_Error.  After replace g_warning() by g_debug(), the problem
is resolved.  This is a workaround for esx5.1x.

Signed-off-by: Dmitry Torokhov <dtor@vmware.com>

diff --git a/open-vm-tools/lib/rpcChannel/rpcChannel.c b/open-vm-tools/lib/rpcChannel/rpcChannel.c
index 45d9358a7926882c7d8fc73481993617ae7cb673..fc39540fbe3b0588a813af71579a57611b2ed76b 100644 (file)
--- a/open-vm-tools/lib/rpcChannel/rpcChannel.c
+++ b/open-vm-tools/lib/rpcChannel/rpcChannel.c
@@ -461,7 +461,11 @@ RpcChannel_Error(void *_chan,
 {
    RpcChannelInt *chan = _chan;
    chan->rpcError = TRUE;
-   g_warning("Error in the RPC receive loop: %s.\n", status);
+   /*
+    * XXX: Workaround for PR 935520.
+    * Revert the log call to g_warning() after fixing PR 955746.
+    */
+   g_debug("Error in the RPC receive loop: %s.\n", status);
 
    if (chan->resetCheck == NULL) {
       chan->resetCheck = g_idle_source_new();