summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: a791a08)
raw | patch | inline | side by side (parent: a791a08)
author | Florian Forster <octo@leeloo.lan.home.verplant.org> | |
Sat, 13 Sep 2008 15:32:03 +0000 (17:32 +0200) | ||
committer | Florian Forster <octo@leeloo.lan.home.verplant.org> | |
Sat, 13 Sep 2008 15:32:03 +0000 (17:32 +0200) |
src/collectd.conf.pod | patch | blob | history |
diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod
index aa9dfeb346cc8079f4ec84679a55e2fe17b76454..6f7cebd45d78338fa160aba1c79d3df4365b98f3 100644 (file)
--- a/src/collectd.conf.pod
+++ b/src/collectd.conf.pod
will run serious performance problems. The B<CacheFlush> setting and the
internal update queue assert that collectd continues to work just fine even
under heavy load, but the system may become very unresponsive and slow. This is
-a problem especially if create graphs from the RRD files on the same machine,
-for example using the C<graph.cgi> script included in the
+a problem especially if you create graphs from the RRD files on the same
+machine, for example using the C<graph.cgi> script included in the
C<contrib/collection3/> directory.
This setting is designed for very large setups. Setting this option to a value