projects
/
collectd.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
dda68af
)
Docs: use "its" vice "it's" where appropriate
author
William Pursell
<williamp@wepay.com>
Wed, 10 Jan 2018 00:35:00 +0000
(16:35 -0800)
committer
Florian Forster
<ff@octo.it>
Mon, 19 Mar 2018 16:23:13 +0000
(17:23 +0100)
contrib/exec-munin.px
patch
|
blob
|
history
contrib/exec-nagios.px
patch
|
blob
|
history
contrib/php-collection/functions.php
patch
|
blob
|
history
src/collectd-exec.pod
patch
|
blob
|
history
src/collectd-nagios.pod
patch
|
blob
|
history
src/collectd-threshold.pod
patch
|
blob
|
history
src/collectd-unixsock.pod
patch
|
blob
|
history
src/collectd.pod
patch
|
blob
|
history
src/utils_latency.c
patch
|
blob
|
history
src/write_prometheus.c
patch
|
blob
|
history
diff --git
a/contrib/exec-munin.px
b/contrib/exec-munin.px
index
3e62ce0
..
5309cc6
100755
(executable)
--- a/
contrib/exec-munin.px
+++ b/
contrib/exec-munin.px
@@
-56,7
+56,7
@@
exit (0);
=head1 CONFIGURATION
=head1 CONFIGURATION
-This script reads it
'
s configuration from F</etc/exec-munin.conf>. The
+This script reads its configuration from F</etc/exec-munin.conf>. The
configuration is read using C<Config::General> which understands a Apache-like
config syntax, so it's very similar to the F<collectd.conf> syntax, too.
configuration is read using C<Config::General> which understands a Apache-like
config syntax, so it's very similar to the F<collectd.conf> syntax, too.
diff --git
a/contrib/exec-nagios.px
b/contrib/exec-nagios.px
index
ec13b0a
..
b9758ec
100755
(executable)
--- a/
contrib/exec-nagios.px
+++ b/
contrib/exec-nagios.px
@@
-36,7
+36,7
@@
exit (0);
=head1 CONFIGURATION
=head1 CONFIGURATION
-This script reads it
'
s configuration from F</etc/exec-nagios.conf>. The
+This script reads its configuration from F</etc/exec-nagios.conf>. The
configuration is read using C<Config::General> which understands a Apache-like
config syntax, so it's very similar to the F<collectd.conf> syntax, too.
configuration is read using C<Config::General> which understands a Apache-like
config syntax, so it's very similar to the F<collectd.conf> syntax, too.
diff --git
a/contrib/php-collection/functions.php
b/contrib/php-collection/functions.php
index
fa2badc
..
c063d57
100644
(file)
--- a/
contrib/php-collection/functions.php
+++ b/
contrib/php-collection/functions.php
@@
-536,7
+536,7
@@
function rrd_get_color($code, $line = true) {
}
/**
}
/**
- * Draw RRD file based on it
'
s structure
+ * Draw RRD file based on its structure
* @host
* @plugin
* @pinst
* @host
* @plugin
* @pinst
@@
-635,7
+635,7
@@
function collectd_draw_rrd($host, $plugin, $pinst = null, $type, $tinst = null,
}
/**
}
/**
- * Draw RRD file based on it
'
s structure
+ * Draw RRD file based on its structure
* @timespan
* @host
* @plugin
* @timespan
* @host
* @plugin
diff --git
a/src/collectd-exec.pod
b/src/collectd-exec.pod
index
c65966b
..
b878657
100644
(file)
--- a/
src/collectd-exec.pod
+++ b/
src/collectd-exec.pod
@@
-73,7
+73,7
@@
Each line beginning with a C<#> (hash mark) is ignored.
=item B<PUTVAL> I<Identifier> [I<OptionList>] I<Valuelist>
Submits one or more values (identified by I<Identifier>, see below) to the
=item B<PUTVAL> I<Identifier> [I<OptionList>] I<Valuelist>
Submits one or more values (identified by I<Identifier>, see below) to the
-daemon which will dispatch it to all it
'
s write-plugins.
+daemon which will dispatch it to all its write-plugins.
An I<Identifier> is of the form
C<I<host>B</>I<plugin>B<->I<instance>B</>I<type>B<->I<instance>> with both
An I<Identifier> is of the form
C<I<host>B</>I<plugin>B<->I<instance>B</>I<type>B<->I<instance>> with both
diff --git
a/src/collectd-nagios.pod
b/src/collectd-nagios.pod
index
e28ff4b
..
4ff0bf6
100644
(file)
--- a/
src/collectd-nagios.pod
+++ b/
src/collectd-nagios.pod
@@
-107,7
+107,7
@@
consolidations simply ignore NaN values.
=head1 RETURN VALUE
As usual for Nagios plugins, this program writes a short, one line status
=head1 RETURN VALUE
As usual for Nagios plugins, this program writes a short, one line status
-message to STDOUT and signals success or failure with it
'
s return value. It
+message to STDOUT and signals success or failure with its return value. It
exits with a return value of B<0> for I<success>, B<1> for I<warning> and B<2>
for I<critical>. If the values are not available or some other error occurred,
it returns B<3> for I<unknown>.
exits with a return value of B<0> for I<success>, B<1> for I<warning> and B<2>
for I<critical>. If the values are not available or some other error occurred,
it returns B<3> for I<unknown>.
diff --git
a/src/collectd-threshold.pod
b/src/collectd-threshold.pod
index
35f8a9f
..
14f2c8c
100644
(file)
--- a/
src/collectd-threshold.pod
+++ b/
src/collectd-threshold.pod
@@
-40,7
+40,7
@@
Also, all values that match a threshold are considered to be relevant or
"interesting". As a consequence collectd will issue a notification if they are
not received for B<Timeout> iterations. The B<Timeout> configuration option is
explained in section L<collectd.conf(5)/"GLOBAL OPTIONS">. If, for example,
"interesting". As a consequence collectd will issue a notification if they are
not received for B<Timeout> iterations. The B<Timeout> configuration option is
explained in section L<collectd.conf(5)/"GLOBAL OPTIONS">. If, for example,
-B<Timeout> is set to "2" (the default) and some hosts sends it
'
s CPU statistics
+B<Timeout> is set to "2" (the default) and some hosts sends its CPU statistics
to the server every 60 seconds, a notification will be dispatched after about
120 seconds. It may take a little longer because the timeout is checked only
once each B<Interval> on the server.
to the server every 60 seconds, a notification will be dispatched after about
120 seconds. It may take a little longer because the timeout is checked only
once each B<Interval> on the server.
diff --git
a/src/collectd-unixsock.pod
b/src/collectd-unixsock.pod
index
b241a9f
..
db7000a
100644
(file)
--- a/
src/collectd-unixsock.pod
+++ b/
src/collectd-unixsock.pod
@@
-84,7
+84,7
@@
Example:
=item B<PUTVAL> I<Identifier> [I<OptionList>] I<Valuelist>
Submits one or more values (identified by I<Identifier>, see below) to the
=item B<PUTVAL> I<Identifier> [I<OptionList>] I<Valuelist>
Submits one or more values (identified by I<Identifier>, see below) to the
-daemon which will dispatch it to all it
'
s write-plugins.
+daemon which will dispatch it to all its write-plugins.
An I<Identifier> is of the form
C<I<host>B</>I<plugin>B<->I<instance>B</>I<type>B<->I<instance>> with both
An I<Identifier> is of the form
C<I<host>B</>I<plugin>B<->I<instance>B</>I<type>B<->I<instance>> with both
diff --git
a/src/collectd.pod
b/src/collectd.pod
index
1dd899b
..
60707a1
100644
(file)
--- a/
src/collectd.pod
+++ b/
src/collectd.pod
@@
-69,7
+69,7
@@
Output usage information and exit.
=head1 PLUGINS
=head1 PLUGINS
-As noted above, the real power of collectd lies within it
'
s plugins. A
+As noted above, the real power of collectd lies within its plugins. A
(hopefully complete) list of plugins and short descriptions can be found in the
F<README> file that is distributed with the sourcecode. If you're using a
package it's a good bet to search somewhere near F</usr/share/doc/collectd>.
(hopefully complete) list of plugins and short descriptions can be found in the
F<README> file that is distributed with the sourcecode. If you're using a
package it's a good bet to search somewhere near F</usr/share/doc/collectd>.
diff --git
a/src/utils_latency.c
b/src/utils_latency.c
index
625fc42
..
1d3bf2e
100644
(file)
--- a/
src/utils_latency.c
+++ b/
src/utils_latency.c
@@
-65,7
+65,7
@@
struct latency_counter_s {
* When a value above this range is added, Histogram's range is increased by
* increasing the bin width (note that number of bins remains always at 1000).
* This operation of increasing bin width is little expensive as each bin need
* When a value above this range is added, Histogram's range is increased by
* increasing the bin width (note that number of bins remains always at 1000).
* This operation of increasing bin width is little expensive as each bin need
-* to be visited to update it
'
s count. To reduce frequent change of bin width,
+* to be visited to update its count. To reduce frequent change of bin width,
* new bin width will be the next nearest power of 2. Example: 2, 4, 8, 16, 32,
* 64, 128, 256, 512, 1024, 2048, 5086, ...
*
* new bin width will be the next nearest power of 2. Example: 2, 4, 8, 16, 32,
* 64, 128, 256, 512, 1024, 2048, 5086, ...
*
diff --git
a/src/write_prometheus.c
b/src/write_prometheus.c
index
7c4e59e
..
4c363b2
100644
(file)
--- a/
src/write_prometheus.c
+++ b/
src/write_prometheus.c
@@
-59,7
+59,7
@@
static struct MHD_Daemon *httpd;
static cdtime_t staleness_delta = PROMETHEUS_DEFAULT_STALENESS_DELTA;
static cdtime_t staleness_delta = PROMETHEUS_DEFAULT_STALENESS_DELTA;
-/* Unfortunately, protoc-c doesn't export it
'
s implementation of varint, so we
+/* Unfortunately, protoc-c doesn't export its implementation of varint, so we
* need to implement our own. */
static size_t varint(uint8_t buffer[static VARINT_UINT32_BYTES],
uint32_t value) {
* need to implement our own. */
static size_t varint(uint8_t buffer[static VARINT_UINT32_BYTES],
uint32_t value) {