summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel P. Berrange <berrange@redhat.com>2011-06-28 17:39:02 +0100
committerDaniel P. Berrange <berrange@redhat.com>2011-06-29 11:08:59 +0100
commitd550277ca780083e33824c3762fa0d420c920ca5 (patch)
tree687fbd86f558b79d0123779ba199c9627da0c789
parentFix propagation of RPC errors from streams (diff)
downloadlibvirt-d550277ca780083e33824c3762fa0d420c920ca5.tar.gz
libvirt-d550277ca780083e33824c3762fa0d420c920ca5.tar.bz2
libvirt-d550277ca780083e33824c3762fa0d420c920ca5.zip
Lower logging level when failing to register socket watch
The RPC client treats failure to register a socket watch as non-fatal, since we do not mandate that a libvirt client application provide an event loop implementation. It is thus inappropriate to a log a message at VIR_LOG_WARN * src/rpc/virnetsocket.c: Lower logging level
-rw-r--r--src/rpc/virnetsocket.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/rpc/virnetsocket.c b/src/rpc/virnetsocket.c
index 68d7de7d6..96d2dfd76 100644
--- a/src/rpc/virnetsocket.c
+++ b/src/rpc/virnetsocket.c
@@ -1066,7 +1066,7 @@ int virNetSocketAddIOCallback(virNetSocketPtr sock,
virNetSocketEventHandle,
sock,
NULL)) < 0) {
- VIR_WARN("Failed to register watch on socket %p", sock);
+ VIR_DEBUG("Failed to register watch on socket %p", sock);
return -1;
}
sock->func = func;