X-Git-Url: https://git.tokkee.org/?a=blobdiff_plain;f=program%2Fdoc%2Frrdtune.pod;h=18f478d7153eb0707cdb2550bc7395bf6f92b437;hb=d5893e5d8205d5d81fb8ebc7701b9aada439409f;hp=f96d8d1b01f4b0141cb6cc80c506fbd917e74624;hpb=6a4b4d6f01842d7b0f79d9450b4ce23fe8ffdacf;p=rrdtool-all.git

diff --git a/program/doc/rrdtune.pod b/program/doc/rrdtune.pod
index f96d8d1b..18f478d7 100644
--- a/program/doc/rrdtune.pod
+++ b/program/doc/rrdtune.pod
@@ -31,7 +31,10 @@ database as *UNKNOWN*.
 One application of the B<tune> function is to relax the 
 validation rules on an B<RRD>. This allows to fill a new B<RRD> with
 data available in larger intervals than what you would normally want
-to permit.
+to permit. Be very careful with tune operations for COMPUTE data sources.
+Setting the I<min>, I<max>, and  I<heartbeat> for a COMPUTE data source
+without changing the data source type to a non-COMPUTE B<DST> WILL corrupt
+the data source header in the B<RRD>.
 
 A second application of the B<tune> function is to set or alter parameters
 used by the specialized function B<RRAs> for aberrant behavior detection.
@@ -70,9 +73,9 @@ rename a data source
 Alter the deviation scaling factor for the upper bound of the confidence band
 used internally to calculate violations for the FAILURES B<RRA>. The default
 value is 2. Note that this parameter is not related to graphing confidence
-bounds, that scale factor is specified as a CDEV argument to generate a graph with
-confidence bounds. It need agree with the value used internally by the FAILURES
-B<RRA> (although common sense dictates it should).
+bounds, that scale factor must be specified as a CDEF argument to generate 
+a graph with confidence bounds. It need not agree with the value used internally 
+by the FAILURES B<RRA> (although common sense dictates it should).
 
 =item S<B<--deltaneg> I<scale-value>>