summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorNiko Tyni <ntyni@iki.fi>2005-02-20 22:40:58 +0100
committerNiko Tyni <ntyni@iki.fi>2005-02-20 22:40:58 +0100
commit2d8297b72b98005b7220c1ab47e9eeeb68711ac6 (patch)
treeba0e1772fe8a7f988e853379fd1a2923d6f8a480 /doc
parent41b34e09a8692d9253d39d893ad09fdbfec0353c (diff)
downloadsmokeping-2d8297b72b98005b7220c1ab47e9eeeb68711ac6.tar.gz
smokeping-2d8297b72b98005b7220c1ab47e9eeeb68711ac6.tar.xz
* check at startup that existing RRD files conform to the config specifications -- niko
- new Smokeping::RRDtools module - note in CHANGES and smokeping_upgrade
Diffstat (limited to 'doc')
-rw-r--r--doc/smokeping_upgrade.pod11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/smokeping_upgrade.pod b/doc/smokeping_upgrade.pod
index ac393aa..36587d9 100644
--- a/doc/smokeping_upgrade.pod
+++ b/doc/smokeping_upgrade.pod
@@ -101,6 +101,17 @@ The C<pings> variable now has an enforced minimum value of 3, as the
whole design of Smokeping is based on the idea of sending several probes
and measuring and visualizing the variation between them.
+=item RRD parameter checking
+
+Smokeping now checks at startup that the parameters of any existing RRD files
+match those specified in the configuration file. If there is a discrepancy,
+it will give an error message and refuse to start.
+
+This situation is most likely to happen if you have modified the C<step>
+or C<pings> variables in your configuration file. You'll then have to
+delete the old RRD file or somehow convert it to use the new parameters.
+The C<rrdtune> command might be helpful here.
+
=back
In addition to this, some probes have had minor incompatible changes to