Daniel P. Berrangé 6938cd8830 logging: allow max_len=0 to disable log rollover ... Currently setting max_len=0 causes virtlogd to spin in a busy loop. It is natural to allow this to disable log rollover which can be useful for developers debugging things. Note disabling rollover exposes the host to denial of service from a malicious guest, so must be used with care. Closes https://gitlab.com/libvirt/libvirt/-/issues/85 Reviewed-by: Peter Krempa <pkrempa@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>		2020-10-13 10:51:43 +01:00
..
log_daemon_config.c	logging: use g_new0 instead of VIR_ALLOC	2020-10-01 17:32:15 +02:00
log_daemon_config.h
log_daemon_dispatch.c
log_daemon_dispatch.h
log_daemon.c	logging: use g_new0 instead of VIR_ALLOC	2020-10-01 17:32:15 +02:00
log_daemon.h	logging: Replace virMutex with GMutex	2020-08-21 11:34:23 +01:00
log_handler.c	logging: fix endless loop on EOF	2020-10-02 09:15:53 +03:00
log_handler.h
log_manager.c	logging: use g_new0 instead of VIR_ALLOC	2020-10-01 17:32:15 +02:00
log_manager.h
log_protocol.x
meson.build
test_virtlogd.aug.in
virtlogd-admin.socket.in
virtlogd.aug
virtlogd.conf	logging: allow max_len=0 to disable log rollover	2020-10-13 10:51:43 +01:00
virtlogd.init.in
virtlogd.service.in	src: fix misc spelling errors reported by codespell	2020-10-05 10:28:41 +01:00
virtlogd.socket.in
virtlogd.sysconf