openkylin
/
libvirt
mirror of https://gitee.com/openkylin/libvirt.git
9
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: fix some typos about 'informations' 

s/informations/information

Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
This commit is contained in:
Chen Hanxiao 2013-10-22 11:02:43 +08:00 committed by Eric Blake
parent ae6b5da3d1
commit dc33207dbe
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/bugs.html.in
View File

@ -132,7 +132,7 @@
crash, the simplest is to run the program under gdb, reproduce the crash, the simplest is to run the program under gdb, reproduce the
steps leading to the crash and then issue a gdb "bt -a" command to steps leading to the crash and then issue a gdb "bt -a" command to
get the stack trace, attach it to the bug. Note that for the get the stack trace, attach it to the bug. Note that for the
data to be really useful libvirt debug informations must be present data to be really useful libvirt debug information must be present
for example by installing libvirt debuginfo package on Fedora or for example by installing libvirt debuginfo package on Fedora or
Red Hat Enterprise Linux (with debuginfo-install libvirt) prior Red Hat Enterprise Linux (with debuginfo-install libvirt) prior
to running gdb.</p> to running gdb.</p>
@ -147,11 +147,11 @@
<pre> # ps -o etime,pid `pgrep libvirt` <pre> # ps -o etime,pid `pgrep libvirt`
... note the process id from the output ... note the process id from the output
# gdb /usr/sbin/libvirtd # gdb /usr/sbin/libvirtd
.... some informations about gdb and loading debug data .... some information about gdb and loading debug data
(gdb) attach $the_damon_process_id (gdb) attach $the_damon_process_id
.... ....
(gdb) thread apply all bt (gdb) thread apply all bt
.... informations to attach to the bug .... information to attach to the bug
(gdb) (gdb)
</pre> </pre>

4
docs/logging.html.in
View File

@ -68,7 +68,7 @@
<ul> <ul>
<li>1 or "debug": asking the library to log every message emitted, <li>1 or "debug": asking the library to log every message emitted,
though the filters can be used to avoid filling up the output</li> though the filters can be used to avoid filling up the output</li>
<li>2 or "info": log all non-debugging informations</li> <li>2 or "info": log all non-debugging information</li>
<li>3 or "warn": log warnings and errors, that's the default value</li> <li>3 or "warn": log warnings and errors, that's the default value</li>
<li>4 or "error": log only error messages</li> <li>4 or "error": log only error messages</li>
</ul></li> </ul></li>
@ -89,7 +89,7 @@
<ul> <ul>
<li>4: only errors</li> <li>4: only errors</li>
<li>3: warnings and errors</li> <li>3: warnings and errors</li>
<li>2: informations, warnings and errors</li> <li>2: information, warnings and errors</li>
<li>1: debug and everything</li> <li>1: debug and everything</li>
</ul></li> </ul></li>
<li>log_filters: defines logging filters</li> <li>log_filters: defines logging filters</li>