Imported upstream version 1.4.2.

[pkg-rrdtool.git] / doc / cdeftutorial.txt

diff --git a/doc/cdeftutorial.txt b/doc/cdeftutorial.txt
index cab147dfa4c32b44e4e76a9962a881e327506b74..39713326779e822ec41193f102b88c2e1a4a9685 100644 (file)
--- a/doc/cdeftutorial.txt
+++ b/doc/cdeftutorial.txt
@@ -333,11 +333,11 @@ S\bSo\bom\bme\be e\bex\bxa\bam\bmp\bpl\ble\bes\bs
        router2.rrd) for the bigger part of your stats. You could solve this in
        a few ways:
 
-       ·   While creating the new database, fill it with zeros from the start
+       ·   While creating the new database, fill it with zeros from the start
            to now.  You have to make the database start at or before the least
            recent time in the other database.
 
-       ·   Alternatively, you could use CDEF and alter unknown data to zero.
+       ·   Alternatively, you could use CDEF and alter unknown data to zero.
 
        Both methods have their pros and cons. The first method is troublesome
        and if you want to do that you have to figure it out yourself. It is
@@ -398,12 +398,12 @@ S\bSo\bom\bme\be e\bex\bxa\bam\bmp\bpl\ble\bes\bs
        translated into zero and therefore you won't see that there was a
        problem. This is not good and what you really want to do is:
 
-       ·   If there is unknown data, look at the time that this sample was
+       ·   If there is unknown data, look at the time that this sample was
            taken.
 
-       ·   If the unknown value is before time xxx, make it zero.
+       ·   If the unknown value is before time xxx, make it zero.
 
-       ·   If it is after time xxx, leave it as unknown data.
+       ·   If it is after time xxx, leave it as unknown data.
 
        This is doable: you can compare the time that the sample was taken to
        some known time. Assuming you started to monitor your device on Friday
@@ -611,9 +611,9 @@ S\bSo\bom\bme\be e\bex\bxa\bam\bmp\bpl\ble\bes\bs
        You could combine the two CDEF lines into one (we don't use "allusers")
        if you like.  But there are good reasons for writing two CDEFS:
 
-       ·   It improves the readability of the script.
+       ·   It improves the readability of the script.
 
-       ·   It can be used inside GPRINT to display the total number of users.
+       ·   It can be used inside GPRINT to display the total number of users.
 
        If you choose to combine them, you can substitute the "allusers" in the
        second CDEF with the part after the equal sign from the first line:
@@ -784,4 +784,4 @@ A\bAU\bUT\bTH\bHO\bOR\bR
 
 
 
-1.3.999                           2009-06-09                   CDEFTUTORIAL(1)
+1.4.2                             2009-02-21                   CDEFTUTORIAL(1)