Peter Krempa f0803dae93 (log|lock)daemon: Don't spam logs with IO error messages after client disconnects ... The log and lock protocol don't have an extra handshake to close the connection. Instead they just close the socket. Unfortunately that resulted into a lot of spurious garbage logged to the system log files: 2017-03-17 14:00:09.730+0000: 4714: error : virNetSocketReadWire:1800 : End of file while reading data: Input/output error or in the journal as: Mar 13 16:19:33 xxxx virtlogd[32360]: End of file while reading data: Input/output error Use the new facility in the netserverclient to suppress the IO error report from the virNetSocket layer.		2017-03-17 17:20:22 +01:00
..
domain_lock.c
domain_lock.h
libvirt_lockd.aug
libvirt_sanlock.aug
lock_daemon_config.c
lock_daemon_config.h
lock_daemon_dispatch.c
lock_daemon_dispatch.h
lock_daemon.c	(log|lock)daemon: Don't spam logs with IO error messages after client disconnects	2017-03-17 17:20:22 +01:00
lock_daemon.h
lock_driver_lockd.c
lock_driver_lockd.h
lock_driver_nop.c
lock_driver_nop.h
lock_driver_sanlock.c
lock_driver.h
lock_manager.c
lock_manager.h
lock_protocol.x
lockd.conf
sanlock_helper.c
sanlock.conf
test_libvirt_lockd.aug.in
test_libvirt_sanlock.aug.in
test_virtlockd.aug.in
virtlockd.aug
virtlockd.conf
virtlockd.init.in
virtlockd.pod
virtlockd.service.in
virtlockd.socket.in
virtlockd.sysconf