It's required for support purposes. When something goes wrong we collect all
the logs from the hosts, this way we can figure out whats wrong without
requiring someone to reproduce the problem with the logging turned on.
We are working on making the logs easier to filter when inspecting them.
But the general idea is, if the information is in when can easily get it out,
but doing it the other way around is impossible.
In a nutshell order to filter out debug messages grep -v is you friend.
----- Original Message -----
> From: "Peter Portante" <pport...@redhat.com>
> To: firstname.lastname@example.org
> Sent: Thursday, April 5, 2012 10:51:15 AM
> Subject: [vdsm] /etc/rc.c/init.d/vdsmd set filters for libvirt at DEBUG level
> Hello Folks,
> I built vdsm from git and installed it on my system, and found that
> vdsm's init scripts are setting libvirt's logging levels to debug.
> I was quite puzzled for a time trying to modify libvirt's config file
> to reduce the logging levels to warning, as it seemed that the vdsm
> install had placed proper settings in the libvirt config file
> Is there some history behind this log filter setting in the init
> scripts of vdsm that I should know about? Is the debug logging level
> of libvirt required for the correct operation of vdsm?
> vdsm-devel mailing list
vdsm-devel mailing list