source/collectd
1
0
Fork 0
mirror of https://github.com/collectd/collectd.git synced 2026-02-09 04:09:15 +08:00
Code Issues Packages Projects Releases Wiki Activity

Propose fix some typos

Browse Source
This commit is contained in:
John Eismeier
2018-02-13 13:52:43 -05:00
parent 21df6c124e
commit 03003c78f5
3 changed files with 6 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
contrib/sles10.1/collectd.spec
View File

@@ -14,7 +14,7 @@ Vendor: Florian octo Forster <octo@verplant.org>
%description
collectd is a small daemon written in C for performance. It reads various
system statistics and updates RRD files, creating them if neccessary.
system statistics and updates RRD files, creating them if necessary.
Since the daemon doesn't need to startup every time it wants to update the
files it's very fast and easy on the system. Also, the statistics are very
fine grained since the files are updated every 10 seconds.

4
contrib/snmp-probe-host.px
View File

@@ -306,9 +306,9 @@ snmp-probe-host.px - Find out what information an SNMP device provides.
The C<snmp-probe-host.px> script can be used to automatically generate SNMP
configuration snippets for collectd's snmp plugin (see L<collectd-snmp(5)>).
This script parses the collectd configuration and detecs all "data" blocks that
This script parses the collectd configuration and detects all "data" blocks that
are defined for the SNMP plugin. It then queries the device specified on the
command line for all OIDs and registeres which OIDs could be answered correctly
command line for all OIDs and registers which OIDs could be answered correctly
and which resulted in an error. With that information the script figures out
which "data" blocks can be used with this hosts and prints an appropriate
"host" block to standard output.

7
docs/README.virt.md
View File

@@ -43,7 +43,7 @@ Collectd will just use the domain tags, but never enforces or requires them.
It is up to an external entity, like a software management system,
to attach and manage the tags to the domain.
Please note that unless you have such tag-aware management sofware,
Please note that unless you have such tag-aware management software,
it most likely make no sense to enable more than one reader instance on your
setup.
@@ -179,8 +179,8 @@ API, but it is rather a byproduct of how libvirt and QEMU interact.
Whenever we query more than one VM, we should take care to avoid that one blocked VM prevent other,
well behaving VMs to be queried. We don't want one rogue VM to disrupt well-behaving VMs.
Unfortunately, any way we enumerate VMs, either implicitely, using the libvirt bulk stats API,
or explicitely, listing all libvirt domains and query each one in turn, we may unpredictably encounter
Unfortunately, any way we enumerate VMs, either implicitly, using the libvirt bulk stats API,
or explicitly, listing all libvirt domains and query each one in turn, we may unpredictably encounter
one unresponsive VM.
There are many possible approaches to deal with this issue. The virt plugin supports
@@ -237,4 +237,3 @@ The QEMU core, including the handling of the QMP protocol, is single-threaded.
All the above combined make it possible for a client to block forever waiting for one QMP
request, if QEMU itself is blocked. The most likely cause of block is I/O, and this is especially
true considering how QEMU is used in a datacenter.