libvirt/src/logging/test_virtlogd.aug.in

module Test_virtlogd =
   ::CONFIG::

   test Virtlogd.lns get conf =
        { "log_level" = "3" }
        { "log_filters" = "1:logging 4:object 4:json 4:event 1:util" }
        { "log_outputs" = "3:syslog:virtlogd" }
        { "max_clients" = "1024" }
        { "admin_max_clients" = "5" }
        { "max_size" = "2097152" }
        { "max_backups" = "3" }
Import stripped down virtlockd code as basis of virtlogd Copy the virtlockd codebase across to form the initial virlogd code. Simple search & replace of s/lock/log/ and gut the remote protocol & dispatcher. This gives us a daemon that starts up and listens for connections, but does nothing with them. Signed-off-by: Daniel P. Berrange <berrange@redhat.com> 2015-02-09 16:35:05 +00:00			`module Test_virtlogd =`
rpc: avoid duplicating config in virtlockd/virtlogd augeas tests Most of the augeas test files use ::CONFIG:: to pull in the master config file for testing. This ensures that entries added to the config file are actually tested by augeas. This identified the missing admin_max_clients example in the virtlogd config file, which in turn prompted a change in description of the max_clients parameter, since these daemons don't have separate readonly & readwrite sockets. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> 2018-03-21 16:41:10 +00:00			`::CONFIG::`
Import stripped down virtlockd code as basis of virtlogd Copy the virtlockd codebase across to form the initial virlogd code. Simple search & replace of s/lock/log/ and gut the remote protocol & dispatcher. This gives us a daemon that starts up and listens for connections, but does nothing with them. Signed-off-by: Daniel P. Berrange <berrange@redhat.com> 2015-02-09 16:35:05 +00:00
			`test Virtlogd.lns get conf =`
			`{ "log_level" = "3" }`
log: update docs for daemons to improve user understanding Strongly recommend against use of the log_levels setting since it creates overly verbose logs and has a serious performance impact. Describe the log filter syntax better and mention use of shell glob syntax. Also provide more realistic example of good settings to use. The libvirtd example is biased towards QEMU, but when the drivers split off each daemon can get its own more appropriate example. Reviewed-by: John Ferlan <jferlan@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> 2018-04-20 16:52:04 +00:00			`{ "log_filters" = "1:logging 4:object 4:json 4:event 1:util" }`
Import stripped down virtlockd code as basis of virtlogd Copy the virtlockd codebase across to form the initial virlogd code. Simple search & replace of s/lock/log/ and gut the remote protocol & dispatcher. This gives us a daemon that starts up and listens for connections, but does nothing with them. Signed-off-by: Daniel P. Berrange <berrange@redhat.com> 2015-02-09 16:35:05 +00:00			`{ "log_outputs" = "3:syslog:virtlogd" }`
rpc: avoid duplicating config in virtlockd/virtlogd augeas tests Most of the augeas test files use ::CONFIG:: to pull in the master config file for testing. This ensures that entries added to the config file are actually tested by augeas. This identified the missing admin_max_clients example in the virtlogd config file, which in turn prompted a change in description of the max_clients parameter, since these daemons don't have separate readonly & readwrite sockets. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> 2018-03-21 16:41:10 +00:00			`{ "max_clients" = "1024" }`
			`{ "admin_max_clients" = "5" }`
			`{ "max_size" = "2097152" }`
virtlogd: make max file size & number of backups configurable Currently virtlogd has a hardcoded max file size of 128kb and max of 3 backups. This adds two new config parameters to /etc/libvirt/virtlogd.conf to let these be customized. Signed-off-by: Daniel P. Berrange <berrange@redhat.com> 2016-07-01 16:40:55 +00:00			`{ "max_backups" = "3" }`