mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-01-22 04:25:18 +00:00
docs: update to properly reflect meaning of fields in log filter
The documentation (and comment in libvirtd.conf) says that the text in a log filter is compared to the "source file name", and gives the example of "util/json", but this is not correct (at least not since commit 2835c1e, possibly earlier). It is instead compared to the string given in the VIR_LOG_INIT() macro invocation at the top of each source file, which is always "similar to but not the same as" the source file name (in the example above, the proper name is "util.json", while the file name is "util/virjson.c"). This patch corrects the misstatement in both the documentation and in libvirtd.conf.
This commit is contained in:
parent
3d64a9d783
commit
79e7872530
@ -344,10 +344,16 @@
|
|||||||
# The format for a filter is one of:
|
# The format for a filter is one of:
|
||||||
# x:name
|
# x:name
|
||||||
# x:+name
|
# x:+name
|
||||||
# where name is a string which is matched against source file name,
|
|
||||||
# e.g., "remote", "qemu", or "util/json", the optional "+" prefix
|
# where name is a string which is matched against the category
|
||||||
# tells libvirt to log stack trace for each message matching name,
|
# given in the VIR_LOG_INIT() at the top of each libvirt source
|
||||||
# and x is the minimal level where matching messages should be logged:
|
# file, e.g., "remote", "qemu", or "util.json" (the name in the
|
||||||
|
# filter can be a substring of the full category name, in order
|
||||||
|
# to match multiple similar categories), the optional "+" prefix
|
||||||
|
# tells libvirt to log stack trace for each message matching
|
||||||
|
# name, and x is the minimal level where matching messages should
|
||||||
|
# be logged:
|
||||||
|
|
||||||
# 1: DEBUG
|
# 1: DEBUG
|
||||||
# 2: INFO
|
# 2: INFO
|
||||||
# 3: WARNING
|
# 3: WARNING
|
||||||
|
@ -104,12 +104,15 @@
|
|||||||
<pre>
|
<pre>
|
||||||
x:name (log message only)
|
x:name (log message only)
|
||||||
x:+name (log message + stack trace)</pre>
|
x:+name (log message + stack trace)</pre>
|
||||||
<p>where <code>name</code> is a string which is matched against source
|
<p>where <code>name</code> is a string which is matched against
|
||||||
file name, e.g., <code>remote</code>, <code>qemu</code>, or
|
the category given in the VIR_LOG_INIT() at the top of each
|
||||||
<code>util/json</code>, the optional <code>+</code> prefix tells libvirt
|
libvirt source file, e.g., <code>remote</code>, <code>qemu</code>,
|
||||||
to log stack trace for each message matching <code>name</code>, and
|
or <code>util.json</code> (the name in the filter can be a
|
||||||
<code>x</code> is the minimal level where matching messages should
|
substring of the full category name, in order to match multiple
|
||||||
be logged:</p>
|
similar categories), the optional <code>+</code> prefix tells
|
||||||
|
libvirt to log stack trace for each message
|
||||||
|
matching <code>name</code>, and <code>x</code> is the minimal
|
||||||
|
level where matching messages should be logged:</p>
|
||||||
<ul>
|
<ul>
|
||||||
<li>1: DEBUG</li>
|
<li>1: DEBUG</li>
|
||||||
<li>2: INFO</li>
|
<li>2: INFO</li>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user