[libvirt] [PATCH 3/9] Lower logging level when failing to register socket watch
Daniel P. Berrange
berrange at redhat.com
Tue Jun 28 17:01:53 UTC 2011
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
---
src/rpc/virnetsocket.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/rpc/virnetsocket.c b/src/rpc/virnetsocket.c
index 68d7de7..96d2dfd 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;
--
1.7.4.4
More information about the libvir-list
mailing list