summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 6ba08d7)
raw | patch | inline | side by side (parent: 6ba08d7)
author | Michael Renzmann <mrenzmann@madwifi.org> | |
Sat, 4 Aug 2007 10:22:54 +0000 (12:22 +0200) | ||
committer | Florian Forster <octo@leeloo.lan.home.verplant.org> | |
Sat, 4 Aug 2007 10:22:54 +0000 (12:22 +0200) |
src/collectd.pod | patch | blob | history |
diff --git a/src/collectd.pod b/src/collectd.pod
index aae4315416c49f07e37f3dadca5cb421ff63e38a..d5bd792f284877211977641069307e0db7a49b56 100644 (file)
--- a/src/collectd.pod
+++ b/src/collectd.pod
C<network plugin>, for example, is able to send (i.E<nbsp>e. "write") B<and>
receive (i.E<nbsp>e. "dispatch") values. Also, it opens a socket upon
initialization and dispatches the values when it receives them and isn't
-triggered at the same time the input plugins are being read. You can think if
+triggered at the same time the input plugins are being read. You can think of
the network receive part as working asynchronous if it helps.
In addition to the above, there are "logging plugins". Right now those are the