The examples from the rrd graph manual page

change

DEF:a=router1.rrd:link1in:AVERAGE
    DEF:b=router1.rrd:link2in:AVERAGE
@@ -242,7 +242,7 @@
 not matter if you add a to b and then add c to the result or first
 add b to c and then add a to the result. This makes it possible to
 rewrite the RPN into CDEF:result=a,b,c,d,e,+,+,+,+ which is
-evaluatated differently:
+evaluated differently:
     push value of variable a on the stack: a
    push value of variable b on the stack: a b
@@ -277,9 +277,9 @@
 easy to write it in RPN: result=a,b,c,+,*. Note that this is very
 similar to one of the expressions in the previous paragraph, only the
 multiplication and the addition changed places.
-When you have problems with RPN or when rrdtool is complaining, it's 
+
When you have problems with RPN or when RRDTool is complaining, it's 
 usually a Good Thing to write down the stack on a piece of paper
-and see what happens. Have the manual ready and pretend to be rrdtool.
+and see what happens. Have the manual ready and pretend to be RRDTool.
 Just do all the math by hand to see what happens, I'm sure this will
 solve most, if not all, problems you encounter.
 
@@ -290,7 +290,7 @@
 
 The unknown value
 Sometimes collecting your data will fail. This can be very common,
-especially when querying over busy links. RRDtool can be configured
+especially when querying over busy links. RRDTool can be configured
 to allow for one (or even more) unknown value and calculate the missing
 update. You can, for instance, query your device every minute. This is
 creating one so called PDP or primary data point per minute. If you
@@ -358,10 +358,10 @@
 because by definition you would never reach the infinite value. You could
 think of positive and negative infinity (I'm not sure if mathematicians
 will agree) depending on the position relative to zero.
-RRDtool is capable of representing (-not- graphing!) infinity by stopping
+
RRDTool is capable of representing (-not- graphing!) infinity by stopping
 at its current maximum (for positive infinity) or minimum (for negative
 infinity) without knowing this maximum (minimum).
-Infinity in rrdtool is mostly used to draw an AREA without knowing its
+
Infinity in RRDTool is mostly used to draw an AREA without knowing its
 vertical dimensions. You can think of it as drawing an AREA with an
 infinite height and displaying only the part that is visible in the
 current graph. This is probably a good way to approximate infinity
@@ -401,8 +401,8 @@
 possible to create a database filled with zeros, you have to put them in
 on purpose. Implementing the second method is described next:
 What we want is: ``if the value is unknown, replace it with zero''. This
-could be writte in pseudo-code as:  if (value is unknown) then (zero)
-else (value). When reading the rrdgraph manual you notice the ``UN''
+could be written in pseudo-code as:  if (value is unknown) then (zero)
+else (value). When reading the the rrdgraph manpage manual you notice the ``UN''
 function that returns zero or one. You also notice the ``IF'' function
 that takes zero or one as input.
 First look at the ``IF'' function. It takes three values from the stack,
@@ -420,9 +420,9 @@
 
We now combine them: result=value,UN,a,b,IF and when we fill in the
 appropriate things for ``a'' and ``b'' we're finished:
 CDEF:result=value,UN,0,value,IF
-You may want to read Steve Raders RPN guide if you have difficulties
+
You may want to read Steve Rader's RPN guide if you have difficulties
 with the way I explained this last example.
-If you want to check this RPN expression, just mimic rrdtools behavior:
+If you want to check this RPN expression, just mimic RRDTool behavior:
     For any known value, the expression evaluates as follows:
    CDEF:result=value,UN,0,value,IF  (value,UN) is not true so it becomes 0
@@ -494,7 +494,7 @@
 a constant number, we need ``GT''. The output of ``GT'' is true or false
 and this is good input to ``IF''. We want ``if (time > 937521357) then
 (return a) else (return b)''.
-This process was already described toroughly in the previous chapter
+
This process was already described thoroughly in the previous chapter
 so lets do it quick:
     if (x) then a else b
@@ -533,7 +533,7 @@
 or
 Pseudo code: if (number > 100) then 100 else number.
 The second ``problem'' may also be solved by using the rigid option of
-rrdtool graph, however this has not the same result. In this example
+RRDTool graph, however this has not the same result. In this example
 you can end up with a graph that does autoscaling. Also, if you use
 the numbers to display maxima they will be set to 100kb/s.
 We use ``IF'' and ``GT'' again. ``if (x) then (y) else (z)'' is written
@@ -561,7 +561,7 @@
 
These two parts of the CDEF produce either 0 for false or 1 for true.
 We can now check if they are both 0 (or 1) using a few IF statements
 but, as Wataru Satoh pointed out, we can use the ``*'' or ``+'' functions
-as locical AND and locical OR.
+as logical AND and logical OR.
 For ``*'', the result will be zero (false) if either one of the two
 operators is zero.  For ``+'', the result will only be false (0) when
 two false (0) operators will be added.  Warning: *any* number not
@@ -639,7 +639,7 @@
 will be drawn and because it starts at the X-axis and has infinite height
 it will effectively overwrite the STACKed parts.
 You could combine the two CDEF lines into one (we don't use ``allusers'')
-if you like.  But there are good reasons for writting two CDEFS:
+if you like.  But there are good reasons for writing two CDEFS:
 
 
 It improves the readability of the script
@@ -661,10 +661,10 @@
 
 
 
-The examples from the rrd graph manual page
+The examples from the RRD graph manual page
 
 
-Degrees Celcius vs. Degrees Fahrenheit
+Degrees Celsius vs. Degrees Fahrenheit
     rrdtool graph demo.gif --title="Demo Graph" \
       DEF:cel=demo.rrd:exhaust:AVERAGE \
@@ -683,7 +683,7 @@
    4. push 0.5555
    5. push function "multiply" and process it
    6. the resulting value is now "(cel-32)*0.55555"
-Note that if you take the celcius to fahrenheit function you should
+
Note that if you take the Celsius to Fahrenheit function you should
 be doing ``5/9*(cel-32)'' so 0.55555 is not exactly correct. It is close
 enough for this purpose and it saves a calculation.
 
@@ -753,7 +753,7 @@
 We now have to process the rest of the RPN and this is only a simple
 ``IF'' function that returns either ``INF'' or ``UNKN'' depending on the
 time. This is returned to variable ``background''.
-The second CDEF has been discussed earlyer in this document so we
+
The second CDEF has been discussed earlier in this document so we
 won't do that here.
 Now you can draw the different layers. Start with the background
 that is either unknown (nothing to see) or infinite (the whole
@@ -806,7 +806,7 @@
 
 
 SEE ALSO
-The RRDtool manpages
+The RRDTool manpages
 
 
 

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/cdeftutorial.pod
==============================================================================

--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/cdeftutorial.pod	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/cdeftutorial.pod	Thu Jan 15 15:49:42 2004
@@ -15,12 +15,12 @@
 
 =head2 Why this tutorial ?
 
-One of the powerful parts of RRDtool is its ability to do all sorts
+One of the powerful parts of RRDTool is its ability to do all sorts
 of calculations on the data retrieved from it's databases. However
-RRDtool's many options and syntax make it difficult for the average
+RRDTool's many options and syntax make it difficult for the average
 user to understand. The manuals are good at explaining what these
 options do; however they do not (and should not) explain in detail
-why they are useful. As with my RRDtool tutorial: if you want a
+why they are useful. As with my RRDTool tutorial: if you want a
 simple document in simple language you should read this tutorial.
 If you are happy with the official documentation, you may find this
 document too simple or even boring. If you do choose to read this
@@ -76,7 +76,7 @@
 (things-to-do) on the stack and this stack is then processed. The result
 will be placed on the stack. At the end, there should be exactly one
 number left: the outcome of the series of operations. If there is not
-exactly one number left, rrdtool will complain loudly.
+exactly one number left, RRDTool will complain loudly.
 
 Above multiplication by eight will look like:
 
@@ -182,11 +182,11 @@
    --------------------   +
    (outcome of the sum)
 
-As a mathmatical function, this could be written:
+As a mathematical function, this could be written:
 
 C
 
-With RRDtool and RPN, first, define the inputs:
+With RRDTool and RPN, first, define the inputs:
 
    DEF:a=router1.rrd:link1in:AVERAGE
    DEF:b=router1.rrd:link2in:AVERAGE
@@ -216,7 +216,7 @@
 not matter if you add a to b and then add c to the result or first
 add b to c and then add a to the result. This makes it possible to
 rewrite the RPN into C which is
-evaluatated differently: 
+evaluated differently: 
 
    push value of variable a on the stack: a
    push value of variable b on the stack: a b
@@ -257,9 +257,9 @@
 similar to one of the expressions in the previous paragraph, only the
 multiplication and the addition changed places.
 
-When you have problems with RPN or when rrdtool is complaining, it's 
+When you have problems with RPN or when RRDTool is complaining, it's 
 usually a Good Thing to write down the stack on a piece of paper
-and see what happens. Have the manual ready and pretend to be rrdtool.
+and see what happens. Have the manual ready and pretend to be RRDTool.
 Just do all the math by hand to see what happens, I'm sure this will
 solve most, if not all, problems you encounter.
 
@@ -268,7 +268,7 @@
 =head2 The unknown value
 
 Sometimes collecting your data will fail. This can be very common,
-especially when querying over busy links. RRDtool can be configured
+especially when querying over busy links. RRDTool can be configured
 to allow for one (or even more) unknown value and calculate the missing
 update. You can, for instance, query your device every minute. This is
 creating one so called PDP or primary data point per minute. If you
@@ -349,11 +349,11 @@
 think of positive and negative infinity (I'm not sure if mathematicians
 will agree) depending on the position relative to zero.
 
-RRDtool is capable of representing (-not- graphing!) infinity by stopping
+RRDTool is capable of representing (-not- graphing!) infinity by stopping
 at its current maximum (for positive infinity) or minimum (for negative
 infinity) without knowing this maximum (minimum).
 
-Infinity in rrdtool is mostly used to draw an AREA without knowing its
+Infinity in RRDTool is mostly used to draw an AREA without knowing its
 vertical dimensions. You can think of it as drawing an AREA with an
 infinite height and displaying only the part that is visible in the
 current graph. This is probably a good way to approximate infinity
@@ -399,8 +399,8 @@
 on purpose. Implementing the second method is described next:
 
 What we want is: "if the value is unknown, replace it with zero". This
-could be writte in pseudo-code as:  if (value is unknown) then (zero)
-else (value). When reading the rrdgraph manual you notice the "UN"
+could be written in pseudo-code as:  if (value is unknown) then (zero)
+else (value). When reading the L manual you notice the "UN"
 function that returns zero or one. You also notice the "IF" function
 that takes zero or one as input.
 
@@ -425,10 +425,10 @@
 
 C
 
-You may want to read Steve Raders RPN guide if you have difficulties
+You may want to read Steve Rader's RPN guide if you have difficulties
 with the way I explained this last example.
 
-If you want to check this RPN expression, just mimic rrdtools behavior:
+If you want to check this RPN expression, just mimic RRDTool behavior:
 
    For any known value, the expression evaluates as follows:
    CDEF:result=value,UN,0,value,IF  (value,UN) is not true so it becomes 0
@@ -522,7 +522,7 @@
 and this is good input to "IF". We want "if (time > 937521357) then
 (return a) else (return b)".
 
-This process was already described toroughly in the previous chapter
+This process was already described thoroughly in the previous chapter
 so lets do it quick:
 
    if (x) then a else b
@@ -571,7 +571,7 @@
 Pseudo code: if (number > 100) then 100 else number.
 
 The second "problem" may also be solved by using the rigid option of
-rrdtool graph, however this has not the same result. In this example
+RRDTool graph, however this has not the same result. In this example
 you can end up with a graph that does autoscaling. Also, if you use
 the numbers to display maxima they will be set to 100kb/s.
 
@@ -603,7 +603,7 @@
 These two parts of the CDEF produce either 0 for false or 1 for true.
 We can now check if they are both 0 (or 1) using a few IF statements
 but, as Wataru Satoh pointed out, we can use the "*" or "+" functions
-as locical AND and locical OR.
+as logical AND and logical OR.
 
 For "*", the result will be zero (false) if either one of the two
 operators is zero.  For "+", the result will only be false (0) when
@@ -694,7 +694,7 @@
 it will effectively overwrite the STACKed parts.
 
 You could combine the two CDEF lines into one (we don't use "allusers")
-if you like.  But there are good reasons for writting two CDEFS:
+if you like.  But there are good reasons for writing two CDEFS:
 
 =over 4
 
@@ -721,9 +721,9 @@
    GPRINT:allusers:AVERAGE:"Average: %6.0lf"
    GPRINT:allusers:LAST:"Current: %6.0lf\n"
 
-=head1 The examples from the rrd graph manual page
+=head1 The examples from the RRD graph manual page
 
-=head2 Degrees Celcius vs. Degrees Fahrenheit
+=head2 Degrees Celsius vs. Degrees Fahrenheit
 
    rrdtool graph demo.gif --title="Demo Graph" \
       DEF:cel=demo.rrd:exhaust:AVERAGE \
@@ -744,7 +744,7 @@
    5. push function "multiply" and process it
    6. the resulting value is now "(cel-32)*0.55555"
 
-Note that if you take the celcius to fahrenheit function you should
+Note that if you take the Celsius to Fahrenheit function you should
 be doing "5/9*(cel-32)" so 0.55555 is not exactly correct. It is close
 enough for this purpose and it saves a calculation.
 
@@ -820,7 +820,7 @@
 "IF" function that returns either "INF" or "UNKN" depending on the
 time. This is returned to variable "background".
 
-The second CDEF has been discussed earlyer in this document so we
+The second CDEF has been discussed earlier in this document so we
 won't do that here.
 
 Now you can draw the different layers. Start with the background
@@ -875,7 +875,7 @@
 
 =head1 SEE ALSO
 
-The RRDtool manpages
+The RRDTool manpages
 
 =head1 AUTHOR
 

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/cdeftutorial.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/cdeftutorial.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/cdeftutorial.txt	Thu Jan 15 15:49:42 2004
@@ -15,13 +15,13 @@
 
        WWhhyy tthhiiss ttuuttoorriiaall ??
 
-       One of the powerful parts of RRDtool is its ability to do
+       One of the powerful parts of RRDTool is its ability to do
        all sorts of calculations on the data retrieved from it's
-       databases. However RRDtool's many options and syntax make
+       databases. However RRDTool's many options and syntax make
        it difficult for the average user to understand. The manu-
        als are good at explaining what these options do; however
        they do not (and should not) explain in detail why they
-       are useful. As with my RRDtool tutorial: if you want a
+       are useful. As with my RRDTool tutorial: if you want a
        simple document in simple language you should read this
        tutorial.  If you are happy with the official documenta-
        tion, you may find this document too simple or even bor-
@@ -79,7 +79,7 @@
        stack is then processed. The result will be placed on the
        stack. At the end, there should be exactly one number
        left: the outcome of the series of operations. If there is
-       not exactly one number left, rrdtool will complain loudly.
+       not exactly one number left, RRDTool will complain loudly.
 
        Above multiplication by eight will look like:
 
@@ -156,13 +156,13 @@
           --------------------   +
           (outcome of the sum)
 
-       As a mathmatical function, this could be written:
+       As a mathematical function, this could be written:
 
        "add(router1.rrd:link1in , router1.rrd:link2in ,
        router2.rrd:link1in , router3.rrd:link1in ,
        router3.rrd:link2.in)"
 
-       With RRDtool and RPN, first, define the inputs:
+       With RRDTool and RPN, first, define the inputs:
 
           DEF:a=router1.rrd:link1in:AVERAGE
           DEF:b=router1.rrd:link2in:AVERAGE
@@ -193,8 +193,8 @@
        It does not matter if you add a to b and then add c to the
        result or first add b to c and then add a to the result.
        This makes it possible to rewrite the RPN into
-       "CDEF:result=a,b,c,d,e,+,+,+,+" which is evaluatated dif-
-       ferently:
+       "CDEF:result=a,b,c,d,e,+,+,+,+" which is evaluated differ-
+       ently:
 
           push value of variable a on the stack: a
           push value of variable b on the stack: a b
@@ -239,10 +239,10 @@
        of the expressions in the previous paragraph, only the
        multiplication and the addition changed places.
 
-       When you have problems with RPN or when rrdtool is com-
+       When you have problems with RPN or when RRDTool is com-
        plaining, it's usually a Good Thing to write down the
        stack on a piece of paper and see what happens. Have the
-       manual ready and pretend to be rrdtool.  Just do all the
+       manual ready and pretend to be RRDTool.  Just do all the
        math by hand to see what happens, I'm sure this will solve
        most, if not all, problems you encounter.
 
@@ -250,7 +250,7 @@
        TThhee uunnkknnoowwnn vvaalluuee
 
        Sometimes collecting your data will fail. This can be very
-       common, especially when querying over busy links. RRDtool
+       common, especially when querying over busy links. RRDTool
        can be configured to allow for one (or even more) unknown
        value and calculate the missing update. You can, for
        instance, query your device every minute. This is creating
@@ -337,12 +337,12 @@
        tive infinity (I'm not sure if mathematicians will agree)
        depending on the position relative to zero.
 
-       RRDtool is capable of representing (-not- graphing!)
+       RRDTool is capable of representing (-not- graphing!)
        infinity by stopping at its current maximum (for positive
        infinity) or minimum (for negative infinity) without know-
        ing this maximum (minimum).
 
-       Infinity in rrdtool is mostly used to draw an AREA without
+       Infinity in RRDTool is mostly used to draw an AREA without
        knowing its vertical dimensions. You can think of it as
        drawing an AREA with an infinite height and displaying
        only the part that is visible in the current graph. This
@@ -386,7 +386,7 @@
        Implementing the second method is described next:
 
        What we want is: "if the value is unknown, replace it with
-       zero". This could be writte in pseudo-code as:  if (value
+       zero". This could be written in pseudo-code as:  if (value
        is unknown) then (zero) else (value). When reading the
        rrdgraph manual you notice the "UN" function that returns
        zero or one. You also notice the "IF" function that takes
@@ -417,11 +417,11 @@
 
        "CDEF:result=value,UN,0,value,IF"
 
-       You may want to read Steve Raders RPN guide if you have
+       You may want to read Steve Rader's RPN guide if you have
        difficulties with the way I explained this last example.
 
-       If you want to check this RPN expression, just mimic rrd-
-       tools behavior:
+       If you want to check this RPN expression, just mimic RRD-
+       Tool behavior:
 
           For any known value, the expression evaluates as follows:
           CDEF:result=value,UN,0,value,IF  (value,UN) is not true so it becomes 0
@@ -502,8 +502,8 @@
        input to "IF". We want "if (time > 937521357) then (return
        a) else (return b)".
 
-       This process was already described toroughly in the previ-
-       ous chapter so lets do it quick:
+       This process was already described thoroughly in the pre-
+       vious chapter so lets do it quick:
 
           if (x) then a else b
              where x represents "time>937521357"
@@ -547,7 +547,7 @@
        Pseudo code: if (number > 100) then 100 else number.
 
        The second "problem" may also be solved by using the rigid
-       option of rrdtool graph, however this has not the same
+       option of RRDTool graph, however this has not the same
        result. In this example you can end up with a graph that
        does autoscaling. Also, if you use the numbers to display
        maxima they will be set to 100kb/s.
@@ -581,8 +581,8 @@
        These two parts of the CDEF produce either 0 for false or
        1 for true.  We can now check if they are both 0 (or 1)
        using a few IF statements but, as Wataru Satoh pointed
-       out, we can use the "*" or "+" functions as locical AND
-       and locical OR.
+       out, we can use the "*" or "+" functions as logical AND
+       and logical OR.
 
        For "*", the result will be zero (false) if either one of
        the two operators is zero.  For "+", the result will only
@@ -684,7 +684,7 @@
 
        You could combine the two CDEF lines into one (we don't
        use "allusers") if you like.  But there are good reasons
-       for writting two CDEFS:
+       for writing two CDEFS:
 
        +o   It improves the readability of the script
 
@@ -705,8 +705,8 @@
           GPRINT:allusers:AVERAGE:"Average: %6.0lf"
           GPRINT:allusers:LAST:"Current: %6.0lf\n"
 
-TThhee eexxaammpplleess ffrroomm tthhee rrrrdd ggrraapphh mmaannuuaall ppaaggee
-       DDeeggrreeeess CCeellcciiuuss vvss.. DDeeggrreeeess FFaahhrreennhheeiitt
+TThhee eexxaammpplleess ffrroomm tthhee RRRRDD ggrraapphh mmaannuuaall ppaaggee
+       DDeeggrreeeess CCeellssiiuuss vvss.. DDeeggrreeeess FFaahhrreennhheeiitt
 
           rrdtool graph demo.gif --title="Demo Graph" \
              DEF:cel=demo.rrd:exhaust:AVERAGE \
@@ -733,7 +733,7 @@
           5. push function "multiply" and process it
           6. the resulting value is now "(cel-32)*0.55555"
 
-       Note that if you take the celcius to fahrenheit function
+       Note that if you take the Celsius to Fahrenheit function
        you should be doing "5/9*(cel-32)" so 0.55555 is not
        exactly correct. It is close enough for this purpose and
        it saves a calculation.
@@ -815,7 +815,7 @@
        returns either "INF" or "UNKN" depending on the time. This
        is returned to variable "background".
 
-       The second CDEF has been discussed earlyer in this docu-
+       The second CDEF has been discussed earlier in this docu-
        ment so we won't do that here.
 
        Now you can draw the different layers. Start with the
@@ -874,11 +874,11 @@
        Remember: NNoo ffeeeeddbbaacckk eeqquuaallss nnoo cchhaannggeess!!
 
 SSEEEE AALLSSOO
-       The RRDtool manpages
+       The RRDTool manpages
 
 AAUUTTHHOORR
        Alex van den Bogaerdt 
 
 
 
-1.0.45                      2002-06-20            CDEFTUTORIAL(1)
+1.0.46                      2003-09-14            CDEFTUTORIAL(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rpntutorial.html
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rpntutorial.html	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rpntutorial.html	Thu Jan 15 15:49:42 2004
@@ -27,13 +27,13 @@
 
 
 NAME
-rpntutorial - Reading RRDTtool RPN Expressions by Steve Rader
+rpntutorial - Reading RRDTool RPN Expressions by Steve Rader
 PDF version.

 
 
 DESCRIPTION
-This tutorial should help you get to grips with rrdtool RPN expressions
-as seen in CDEF arguments of rrdtool graph.
+This tutorial should help you get to grips with RRDTool RPN expressions
+as seen in CDEF arguments of RRDTool graph.
 
 
 
@@ -65,7 +65,7 @@
 And the first value to the left of the IF corresponds to the false
 (``Z'') branch.  Read the RPN expression ``X,Y,Z,IF'' from left to
 right like so: ``if X then Y else Z''.
-For example, consider ``1,10,100,IF''.  It looks bizzare to me.
+
For example, consider ``1,10,100,IF''.  It looks bizarre to me.
 But when I read ``if 1 then 10 else 100'' it's crystal clear: 1 is true
 so the answer is 10.  Note that only zero is false; all other values
 are true.  ``2,20,200,IF'' (``if 2 then 20 else 200'') evaluates to 20.
@@ -94,7 +94,7 @@
  1) 1,2,3,+,+    eval is 2,3,+ = 5    result is 1,5,+
  2) 1,5,+        eval is 1,5,+ = 6    result is 6
  3) 6
-Let's use that notation to conviently solve some complex RPN expressions
+
Let's use that notation to conveniently solve some complex RPN expressions
 with multiple logic operators:
   1) 20,10,GT,10,20,IF  eval is 20,10,GT = 1     result is 1,10,20,IF
@@ -183,7 +183,7 @@
     parentheses because the ordering of objects on the stack
     can force the evaluation of addition before multiplication.
 Exercise 4:
-Explain why it is desirable for the RRDtool developers to implement
+
Explain why it is desirable for the RRDTool developers to implement
 RPN notation instead of traditional mathematical notation.
 Answer 4:
 @@ -196,7 +196,7 @@
 
 
 AUTHOR
-steve rader <rader at wiscnet.net>
+
Steve Rader <rader at wiscnet.net>
 
 
 

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rpntutorial.pod
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rpntutorial.pod	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rpntutorial.pod	Thu Jan 15 15:49:42 2004
@@ -1,13 +1,13 @@
 =head1 NAME
 
-rpntutorial - Reading RRDTtool RPN Expressions by Steve Rader
+rpntutorial - Reading RRDTool RPN Expressions by Steve Rader
 
 =for html PDF version.
 
 =head1 DESCRIPTION
 
-This tutorial should help you get to grips with rrdtool RPN expressions
-as seen in CDEF arguments of rrdtool graph.
+This tutorial should help you get to grips with RRDTool RPN expressions
+as seen in CDEF arguments of RRDTool graph.
 
 =head1 Reading Comparison Operators
 
@@ -40,7 +40,7 @@
 ("Z") branch.  Read the RPN expression "X,Y,Z,IF" from left to
 right like so: "if X then Y else Z".
 
-For example, consider "1,10,100,IF".  It looks bizzare to me.
+For example, consider "1,10,100,IF".  It looks bizarre to me.
 But when I read "if 1 then 10 else 100" it's crystal clear: 1 is true
 so the answer is 10.  Note that only zero is false; all other values
 are true.  "2,20,200,IF" ("if 2 then 20 else 200") evaluates to 20.
@@ -72,7 +72,7 @@
  2) 1,5,+        eval is 1,5,+ = 6    result is 6
  3) 6
 
-Let's use that notation to conviently solve some complex RPN expressions
+Let's use that notation to conveniently solve some complex RPN expressions
 with multiple logic operators:
 
  1) 20,10,GT,10,20,IF  eval is 20,10,GT = 1     result is 1,10,20,IF
@@ -183,7 +183,7 @@
 
 Exercise 4:
 
-Explain why it is desirable for the RRDtool developers to implement
+Explain why it is desirable for the RRDTool developers to implement
 RPN notation instead of traditional mathematical notation.
 
 Answer 4:
@@ -197,4 +197,4 @@
 
 =head1 AUTHOR
 
-steve rader Erader at wiscnet.netE
+Steve Rader Erader at wiscnet.netE

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rpntutorial.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rpntutorial.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rpntutorial.txt	Thu Jan 15 15:49:42 2004
@@ -3,12 +3,12 @@
 
 
 NNAAMMEE
-       rpntutorial - Reading RRDTtool RPN Expressions by Steve
+       rpntutorial - Reading RRDTool RPN Expressions by Steve
        Rader
 
 DDEESSCCRRIIPPTTIIOONN
-       This tutorial should help you get to grips with rrdtool
-       RPN expressions as seen in CDEF arguments of rrdtool
+       This tutorial should help you get to grips with RRDTool
+       RPN expressions as seen in CDEF arguments of RRDTool
        graph.
 
 RReeaaddiinngg CCoommppaarriissoonn OOppeerraattoorrss
@@ -44,7 +44,7 @@
        ("Z") branch.  Read the RPN expression "X,Y,Z,IF" from
        left to right like so: "if X then Y else Z".
 
-       For example, consider "1,10,100,IF".  It looks bizzare to
+       For example, consider "1,10,100,IF".  It looks bizarre to
        me.  But when I read "if 1 then 10 else 100" it's crystal
        clear: 1 is true so the answer is 10.  Note that only zero
        is false; all other values are true.  "2,20,200,IF" ("if 2
@@ -77,7 +77,7 @@
         2) 1,5,+        eval is 1,5,+ = 6    result is 6
         3) 6
 
-       Let's use that notation to conviently solve some complex
+       Let's use that notation to conveniently solve some complex
        RPN expressions with multiple logic operators:
 
         1) 20,10,GT,10,20,IF  eval is 20,10,GT = 1     result is 1,10,20,IF
@@ -185,7 +185,7 @@
 
        Exercise 4:
 
-       Explain why it is desirable for the RRDtool developers to
+       Explain why it is desirable for the RRDTool developers to
        implement RPN notation instead of traditional mathematical
        notation.
 
@@ -198,8 +198,8 @@
            likely to have bugs.)
 
 AAUUTTHHOORR
-       steve rader 
+       Steve Rader 
 
 
 
-1.0.45                      2002-02-26             RPNTUTORIAL(1)
+1.0.46                      2003-09-14             RPNTUTORIAL(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrd-beginners.html
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrd-beginners.html	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrd-beginners.html	Thu Jan 15 15:49:42 2004
@@ -19,7 +19,6 @@
 	
 
 		What makes RRDTool so special?
-		Understanding by an example
 		Graphical Magic
 		Wrapping RRDTool within Shell/Perl script
 		
@@ -53,31 +52,31 @@
 databases. With help of an example, it explains structure of RRDTool
 database. This is followed by an overview of the ``graph'' feature of RRDTool.
 At the end, it has sample scripts that illustrates the
-usage/wrapping of RRDTool within Shell/Perl.
+usage/wrapping of RRDTool within Shell or Perl scripts.
 
 
 What makes RRDTool so special?
-RDtool is GNU licensed software developed by Tobies Oetiker, a system
+
RRDTool is GNU licensed software developed by Tobias Oetiker, a system
 manager at the Swiss Federal Institute of Technology. Though it is a
-database, there are distinct differences between RRDtool database and other
+database, there are distinct differences between RRDTool database and other
 databases as listed below:
 
 
-RRDTool stores data; that makes it a back end tool. The RRDtool command set
+RRDTool stores data; that makes it a back end tool. The RRDTool command set
 allows the creation of graphs; that makes it a front end tool as well. Other
 databases just stores data and can not create graphs.
 
 
 In case of linear databases, new data gets appended at the bottom of
-the database table. Thus its size keeps on increasing, whereas size of an RRDtool
-database is determined at creation time. Imagine an RRDtool database as the
+the database table. Thus its size keeps on increasing, whereas size of an RRDTool
+database is determined at creation time. Imagine an RRDTool database as the
 perimeter of a circle. Data is added along the perimeter. When new data
 reaches the starting point, it overwrites existing data. This way, the size of
-an RRDtool database always remains constant. The name ``Round Robin'' stems from this
+an RRDTool database always remains constant. The name ``Round Robin'' stems from this
 attribute.
 
 
-Other databases store the values as supplied. RRDtool can be configured to
+Other databases store the values as supplied. RRDTool can be configured to
 calculate the rate of change from the previous to the current value and
 store this information instead.
 
@@ -89,16 +88,18 @@
 imperative to use scripts that runs at regular intervals to ensure a constant
 data flow to update the RRDTool database.
 
-RRDtool has a lot to do with time. With every data update, it also needs to
+
+
+RRDTool has a lot to do with time. With every data update, it also needs to
 know the time when that update occurred. Time is always expressed in
 seconds passed since epoch (01-01-1971). RRDTool can be installed on Unix as
 well as Windows. It has command set to carry out various
-operations on rrd database. This command set can be accessed from the command line,
-and from shell or perl scripts. The scripts
-act as wrappers for accessing data stored in RRDtool database.
-
-
-Understanding by an example
+operations on RRD database. This command set can be accessed from the command line,
+and from Shell or Perl scripts. The scripts
+act as wrappers for accessing data stored in RRDTool database.
++
+=head2 Understanding by an example
 The structure of an RRD database is different than other linear databases.
 Other databases define tables with columns, and many other parameters. These
 definitions sometime are very complex, especially in large databases.
@@ -137,7 +138,7 @@
 every step interval, a new value of DS is supplied to update the database.
 This value is also called as Primary Data Point (PDP). In our example
 mentioned above, a new PDP is generated every 300 seconds.
-Note, that if you do NOT supply new datapoints exaclty every 300 seconds,
+
Note, that if you do NOT supply new datapoints exactly every 300 seconds,
 this is not problem, RRDTool will interpolate the data accordingly.
 DST (Data Source Type) defines type of DS. It can be COUNTER, DERIVE,
 ABSOLUTE, GAUGE. A DS declared as COUNTER will save the rate of change of
@@ -146,7 +147,7 @@
 counters on a router is an ideal candidate for using COUNTER as DST. DERIVE
 is same as COUNTER but it allows negative values as well. If you want to see
 the rate of change in free diskspace on your server, then you might want to
-use the DERIVE data type. ABSOULTE also saves the rate of change but it assumes
+use the DERIVE data type. ABSOLUTE also saves the rate of change but it assumes
 that previous value is set to 0. The difference between current and previous
 value is always equal to the current value. So, it stores the current value divided
 by step interval (300 seconds in our example). GAUGE does not save the rate of
@@ -162,10 +163,10 @@
  ABSOLUTE DS  =    1,  2,   3,    4 
  GAUGE DS     = 300, 600, 900, 1200
 The next parameter is heartbeat. In our example, heartbeat is 600
-seconds. If database doesn not get a new PDP within 300
+seconds. If database does not get a new PDP within 300
 seconds, it will wait for another 300 seconds (total 600 seconds).
 If it doesnt receive any PDP with in 600 seconds, it will save an UNKNOWN value
-into database. This UNKOWN value is a special feature of RRDTool - it is
+into database. This UNKNOWN value is a special feature of RRDTool - it is
 much better than to assume a missing value was 0 (zero).
 For example, the traffic flow counter on a router
 keeps on increasing. Lets say, a value is missed for an interval and 0 is stored
@@ -193,7 +194,7 @@
 represents an AVERAGE value for a day (288 PDPs, each covering 300 seconds =
 24 hours). Therefore this RRA is an archive for one month. A single database
 can have many RRAs. If there are multiple DSs, each individual RRA will save
-data for all the DSes in the database. For example, if a database has 3 DSs;
+data for all the DSs in the database. For example, if a database has 3 DSs;
 and daily, weekly, monthly, and yearly RRAs are declared, then each RRA will
 hold data from all 3 data sources.
 
@@ -211,14 +212,14 @@
 Bytes. Graphs for these values will be more senseful if values are
 represented in MBytes and mbps. the RRDTool graph command allows to define
 such conversions. Apart from mathematical calculations, it is also possible
-to peform logical operations such as greater than, less than, and if then
+to perform logical operations such as greater than, less than, and if then
 else. If a database contains more than one RRA archive, then a question may
 arise - how does RRDTool decide which RRA archive to use for retrieving the
-values? RRDtool takes looks at several things when making its choice. First
+values? RRDTool takes looks at several things when making its choice. First
 it makes sure that the RRA covers as much of the graphing time frame as
 possible. Second it looks at the resolution of the RRA compared to the
 resolution of the graph. It tries to find one which has the same or better
-resolution. With the ``-r'' option you can force RRDtool to assume a different
+resolution. With the ``-r'' option you can force RRDTool to assume a different
 resolution than the one calculated from the pixel width of the graph.
 Values of different variables can be presented in 5 different shapes in a
 graph - AREA, LINE1, LINE2, LINE3, and STACK. AREA is represented by a solid
@@ -272,7 +273,7 @@
  my $end_time = $cur_time - 86400;     # setting end time to 24 hours behind current time
  my $start_time = $end_time - 2592000; # setting start time to 30 days from end time
 - #fetching average values from rrd database between start and end time
+ #fetching average values from RRD database between start and end time
  my ($start,$step,$ds_names,$data) = 
      RRDs::fetch("target.rrd", "AVERAGE", 
                  "-r", "600", "-s", "$start_time", "-e", "$end_time");
@@ -291,7 +292,7 @@
  my $tot_time = 0;
  my $count = 0;
  #saving values from 2-dimensional into 1-dimensional array
- for $i ( 0 .. $#vals ) 
+ for $i ( 0 .. $#vals ) {
      $tot_mem[$count] = $vals[$i][1];
      $count++;
  }
@@ -334,7 +335,9 @@
 
 
 AUTHOR
-Ketan Patel <k2pattu at yahoo.com>
+Ketan Patel <k2pattu at yahoo.com>
+
+
 
 
 

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrd-beginners.pod
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrd-beginners.pod	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrd-beginners.pod	Thu Jan 15 15:49:42 2004
@@ -13,36 +13,36 @@
 databases. With help of an example, it explains structure of RRDTool
 database. This is followed by an overview of the "graph" feature of RRDTool.
 At the end, it has sample scripts that illustrates the
-usage/wrapping of RRDTool within Shell/Perl.
+usage/wrapping of RRDTool within Shell or Perl scripts.
 
 =head2 What makes RRDTool so special?
 
-RDtool is GNU licensed software developed by Tobies Oetiker, a system
+RRDTool is GNU licensed software developed by Tobias Oetiker, a system
 manager at the Swiss Federal Institute of Technology. Though it is a
-database, there are distinct differences between RRDtool database and other
+database, there are distinct differences between RRDTool database and other
 databases as listed below:
 
 =over
 
 =item *
 
-RRDTool stores data; that makes it a back end tool. The RRDtool command set
+RRDTool stores data; that makes it a back end tool. The RRDTool command set
 allows the creation of graphs; that makes it a front end tool as well. Other
 databases just stores data and can not create graphs.
 
 =item *
 
 In case of linear databases, new data gets appended at the bottom of
-the database table. Thus its size keeps on increasing, whereas size of an RRDtool
-database is determined at creation time. Imagine an RRDtool database as the
+the database table. Thus its size keeps on increasing, whereas size of an RRDTool
+database is determined at creation time. Imagine an RRDTool database as the
 perimeter of a circle. Data is added along the perimeter. When new data
 reaches the starting point, it overwrites existing data. This way, the size of
-an RRDtool database always remains constant. The name "Round Robin" stems from this
+an RRDTool database always remains constant. The name "Round Robin" stems from this
 attribute.
 
 =item *
 
-Other databases store the values as supplied. RRDtool can be configured to
+Other databases store the values as supplied. RRDTool can be configured to
 calculate the rate of change from the previous to the current value and
 store this information instead.
 
@@ -56,15 +56,15 @@
 data flow to update the RRDTool database.
 
 =back
-
-RRDtool has a lot to do with time. With every data update, it also needs to
+  
+RRDTool has a lot to do with time. With every data update, it also needs to
 know the time when that update occurred. Time is always expressed in
 seconds passed since epoch (01-01-1971). RRDTool can be installed on Unix as
 well as Windows. It has command set to carry out various
-operations on rrd database. This command set can be accessed from the command line,
-and from shell or perl scripts. The scripts
-act as wrappers for accessing data stored in RRDtool database.
-
+operations on RRD database. This command set can be accessed from the command line,
+and from Shell or Perl scripts. The scripts
+act as wrappers for accessing data stored in RRDTool database.
+  
 =head2 Understanding by an example
 
 The structure of an RRD database is different than other linear databases.
@@ -111,7 +111,7 @@
 This value is also called as Primary Data Point B<(PDP)>. In our example
 mentioned above, a new PDP is generated every 300 seconds.
 
-Note, that if you do NOT supply new datapoints exaclty every 300 seconds,
+Note, that if you do NOT supply new datapoints exactly every 300 seconds,
 this is not problem, RRDTool will interpolate the data accordingly.
 
 B (Data Source Type) defines type of DS. It can be COUNTER, DERIVE,
@@ -121,7 +121,7 @@
 counters on a router is an ideal candidate for using COUNTER as DST. DERIVE
 is same as COUNTER but it allows negative values as well. If you want to see
 the rate of I in free diskspace on your server, then you might want to
-use the DERIVE data type. ABSOULTE also saves the rate of change but it assumes
+use the DERIVE data type. ABSOLUTE also saves the rate of change but it assumes
 that previous value is set to 0. The difference between current and previous
 value is always equal to the current value. So, it stores the current value divided
 by step interval (300 seconds in our example). GAUGE does not save the rate of
@@ -138,10 +138,10 @@
  GAUGE DS     = 300, 600, 900, 1200
 
 The next parameter is B. In our example, heartbeat is 600
-seconds. If database doesn not get a new PDP within 300
+seconds. If database does not get a new PDP within 300
 seconds, it will wait for another 300 seconds (total 600 seconds).
 If it doesnt receive any PDP with in 600 seconds, it will save an UNKNOWN value
-into database. This UNKOWN value is a special feature of RRDTool - it is
+into database. This UNKNOWN value is a special feature of RRDTool - it is
 much better than to assume a missing value was 0 (zero).
 For example, the traffic flow counter on a router
 keeps on increasing. Lets say, a value is missed for an interval and 0 is stored
@@ -173,7 +173,7 @@
 represents an AVERAGE value for a day (288 PDPs, each covering 300 seconds =
 24 hours). Therefore this RRA is an archive for one month. A single database
 can have many RRAs. If there are multiple DSs, each individual RRA will save
-data for all the DSes in the database. For example, if a database has 3 DSs;
+data for all the DSs in the database. For example, if a database has 3 DSs;
 and daily, weekly, monthly, and yearly RRAs are declared, then each RRA will
 hold data from all 3 data sources.
 
@@ -191,14 +191,14 @@
 Bytes. Graphs for these values will be more senseful if values are
 represented in MBytes and mbps. the RRDTool graph command allows to define
 such conversions. Apart from mathematical calculations, it is also possible
-to peform logical operations such as greater than, less than, and if then
+to perform logical operations such as greater than, less than, and if then
 else. If a database contains more than one RRA archive, then a question may
 arise - how does RRDTool decide which RRA archive to use for retrieving the
-values? RRDtool takes looks at several things when making its choice. First
+values? RRDTool takes looks at several things when making its choice. First
 it makes sure that the RRA covers as much of the graphing time frame as
 possible. Second it looks at the resolution of the RRA compared to the
 resolution of the graph. It tries to find one which has the same or better
-resolution. With the "-r" option you can force RRDtool to assume a different
+resolution. With the "-r" option you can force RRDTool to assume a different
 resolution than the one calculated from the pixel width of the graph.
 
 Values of different variables can be presented in 5 different shapes in a
@@ -251,7 +251,7 @@
  my $end_time = $cur_time - 86400;     # setting end time to 24 hours behind current time
  my $start_time = $end_time - 2592000; # setting start time to 30 days from end time
 
- #fetching average values from rrd database between start and end time
+ #fetching average values from RRD database between start and end time
  my ($start,$step,$ds_names,$data) = 
      RRDs::fetch("target.rrd", "AVERAGE", 
                  "-r", "600", "-s", "$start_time", "-e", "$end_time");
@@ -270,7 +270,7 @@
  my $tot_time = 0;
  my $count = 0;
  #saving values from 2-dimensional into 1-dimensional array
- for $i ( 0 .. $#vals ) 
+ for $i ( 0 .. $#vals ) {
      $tot_mem[$count] = $vals[$i][1];
      $count++;
  }

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrd-beginners.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrd-beginners.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrd-beginners.txt	Thu Jan 15 15:49:42 2004
@@ -16,32 +16,33 @@
        an example, it explains structure of RRDTool database.
        This is followed by an overview of the "graph" feature of
        RRDTool.  At the end, it has sample scripts that illus-
-       trates the usage/wrapping of RRDTool within Shell/Perl.
+       trates the usage/wrapping of RRDTool within Shell or Perl
+       scripts.
 
        WWhhaatt mmaakkeess RRRRDDTTooooll ssoo ssppeecciiaall??
 
-       RDtool is GNU licensed software developed by Tobies
+       RRDTool is GNU licensed software developed by Tobias
        Oetiker, a system manager at the Swiss Federal Institute
        of Technology. Though it is a database, there are distinct
-       differences between RRDtool database and other databases
+       differences between RRDTool database and other databases
        as listed below:
 
        +o   RRDTool stores data; that makes it a back end tool.
-           The RRDtool command set allows the creation of graphs;
+           The RRDTool command set allows the creation of graphs;
            that makes it a front end tool as well. Other
            databases just stores data and can not create graphs.
 
        +o   In case of linear databases, new data gets appended at
            the bottom of the database table. Thus its size keeps
-           on increasing, whereas size of an RRDtool database is
-           determined at creation time. Imagine an RRDtool
+           on increasing, whereas size of an RRDTool database is
+           determined at creation time. Imagine an RRDTool
            database as the perimeter of a circle. Data is added
            along the perimeter. When new data reaches the start-
            ing point, it overwrites existing data. This way, the
-           size of an RRDtool database always remains constant.
+           size of an RRDTool database always remains constant.
            The name "Round Robin" stems from this attribute.
 
-       +o   Other databases store the values as supplied. RRDtool
+       +o   Other databases store the values as supplied. RRDTool
            can be configured to calculate the rate of change from
            the previous to the current value and store this
            information instead.
@@ -55,15 +56,15 @@
            runs at regular intervals to ensure a constant data
            flow to update the RRDTool database.
 
-       RRDtool has a lot to do with time. With every data update,
+       RRDTool has a lot to do with time. With every data update,
        it also needs to know the time when that update occurred.
        Time is always expressed in seconds passed since epoch
        (01-01-1971). RRDTool can be installed on Unix as well as
        Windows. It has command set to carry out various opera-
-       tions on rrd database. This command set can be accessed
-       from the command line, and from shell or perl scripts. The
-       scripts act as wrappers for accessing data stored in RRD-
-       tool database.
+       tions on RRD database. This command set can be accessed
+       from the command line, and from Shell or Perl scripts. The
+       scripts act as wrappers for accessing data stored in
+       RRDTool database.
 
        UUnnddeerrssttaannddiinngg bbyy aann eexxaammppllee
 
@@ -119,7 +120,7 @@
        example mentioned above, a new PDP is generated every 300
        seconds.
 
-       Note, that if you do NOT supply new datapoints exaclty
+       Note, that if you do NOT supply new datapoints exactly
        every 300 seconds, this is not problem, RRDTool will
        interpolate the data accordingly.
 
@@ -132,7 +133,7 @@
        COUNTER as DST. DERIVE is same as COUNTER but it allows
        negative values as well. If you want to see the rate of
        _c_h_a_n_g_e in free diskspace on your server, then you might
-       want to use the DERIVE data type. ABSOULTE also saves the
+       want to use the DERIVE data type. ABSOLUTE also saves the
        rate of change but it assumes that previous value is set
        to 0. The difference between current and previous value is
        always equal to the current value. So, it stores the cur-
@@ -151,11 +152,11 @@
         GAUGE DS     = 300, 600, 900, 1200
 
        The next parameter is hheeaarrttbbeeaatt. In our example, heartbeat
-       is 600 seconds. If database doesn not get a new PDP within
+       is 600 seconds. If database does not get a new PDP within
        300 seconds, it will wait for another 300 seconds (total
        600 seconds).  If it doesnt receive any PDP with in 600
        seconds, it will save an UNKNOWN value into database. This
-       UNKOWN value is a special feature of RRDTool - it is much
+       UNKNOWN value is a special feature of RRDTool - it is much
        better than to assume a missing value was 0 (zero).  For
        example, the traffic flow counter on a router keeps on
        increasing. Lets say, a value is missed for an interval
@@ -195,8 +196,8 @@
        ering 300 seconds = 24 hours). Therefore this RRA is an
        archive for one month. A single database can have many
        RRAs. If there are multiple DSs, each individual RRA will
-       save data for all the DSes in the database. For example,
-       if a database has 3 DSs; and daily, weekly, monthly, and
+       save data for all the DSs in the database. For example, if
+       a database has 3 DSs; and daily, weekly, monthly, and
        yearly RRAs are declared, then each RRA will hold data
        from all 3 data sources.
 
@@ -217,17 +218,17 @@
        for these values will be more senseful if values are rep-
        resented in MBytes and mbps. the RRDTool graph command
        allows to define such conversions. Apart from mathematical
-       calculations, it is also possible to peform logical opera-
-       tions such as greater than, less than, and if then else.
+       calculations, it is also possible to perform logical oper-
+       ations such as greater than, less than, and if then else.
        If a database contains more than one RRA archive, then a
        question may arise - how does RRDTool decide which RRA
-       archive to use for retrieving the values? RRDtool takes
+       archive to use for retrieving the values? RRDTool takes
        looks at several things when making its choice. First it
        makes sure that the RRA covers as much of the graphing
        time frame as possible. Second it looks at the resolution
        of the RRA compared to the resolution of the graph. It
        tries to find one which has the same or better resolution.
-       With the "-r" option you can force RRDtool to assume a
+       With the "-r" option you can force RRDTool to assume a
        different resolution than the one calculated from the
        pixel width of the graph.
 
@@ -261,7 +262,6 @@
 
 
 
-
         #!/bin/sh
         a=0
         while [ "$a" == 0 ]; do
@@ -328,7 +328,7 @@
 
 
 
-        #fetching average values from rrd database between start and end time
+        #fetching average values from RRD database between start and end time
         my ($start,$step,$ds_names,$data) =
             RRDs::fetch("target.rrd", "AVERAGE",
                         "-r", "600", "-s", "$start_time", "-e", "$end_time");
@@ -347,7 +347,7 @@
         my $tot_time = 0;
         my $count = 0;
         #saving values from 2-dimensional into 1-dimensional array
-        for $i ( 0 .. $#vals )
+        for $i ( 0 .. $#vals ) {
             $tot_mem[$count] = $vals[$i][1];
             $count++;
         }
@@ -392,4 +392,4 @@
 
 
 
-1.0.45                      2003-07-21           RRD-BEGINNERS(1)
+1.0.46                      2003-09-14           RRD-BEGINNERS(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdcgi.html
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdcgi.html	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdcgi.html	Thu Jan 15 15:49:42 2004
@@ -18,9 +18,7 @@
 	DESCRIPTION
 	
 
-		Pass 1
-		Pass 2
-		Pass 3
+		Keywords
 	
 
 	EXAMPLE 1
@@ -52,9 +50,16 @@
 rrdcgi parses the contents of the template in 3 steps. In each step it looks
 only for a subset of tags. This allows to nest tags.
 The argument parser uses the same semantics as you are used from your c shell.
+
+--filter

+
+
+Assume that rrdcgi is being run as a filter and not as a cgi.
+
+
 
 
-Pass 1
+Keywords
 
 RRD::CV name

 
@@ -92,11 +97,7 @@
 might give you the name of the remote user given you are using
 some sort of access control on the directory
 
-
-
-
-Pass 2
-
+
 RRD::GOODFOR seconds

 
 
@@ -126,6 +127,18 @@
 values permitted to TZ depend on your OS.
 
 
+RRD::SETVAR variable value

+
+
+Analog to SETENV but for local variables
+
+
+RRD::GETVAR variable

+
+
+Analog to GETENV but for local variables
+
+
 RRD::TIME::LAST rrd-file strftime-format

 
 
@@ -150,16 +163,12 @@
 to allow pretty titles on graphs with times that are easier for non rrdtool
 folks to figure out than ``-2weeks''.
 
-
-
-
-Pass 3
-
+
 RRD::GRAPH rrdgraph arguments

 
 
 This tag creates the RRD graph defined in its argument and then gets
-replaced by an appropriate <IMG> tag referring to the graph.
+replaced by an appropriate <IMG<gt> tag referring to the graph.
 The --lazy option in RRD graph can be used to make sure that graphs
 are only regenerated when they are out of date. The arguments
 to the RRD::GRAPH tag work as described in the rrdgraph manual page.
@@ -179,7 +188,7 @@
 
 
 Note that %s stands for the filename part of the graph generated, all
-directories given in the GIF file argument will get dropped.
+directories given in the PNG file argument will get dropped.
 
 
 RRD::PRINT number


Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdcgi.pod
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdcgi.pod	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdcgi.pod	Thu Jan 15 15:49:42 2004
@@ -24,10 +24,13 @@
 =over 8
 
 
+=item B<--filter>
+
+Assume that rrdcgi is being run as a filter and not as a cgi.
 
 =back
 
-=head2 Pass 1
+=head2 Keywords
 
 =over 8
 
@@ -57,11 +60,6 @@
 might give you the name of the remote user given you are using
 some sort of access control on the directory
 
-=back
-
-=head2 Pass 2
-
-=over 8
 
 =item RRD::GOODFOR I
 
@@ -83,6 +81,14 @@
 to make sure everything is presented in Universal Time. Note that the
 values permitted to TZ depend on your OS.
 
+=item RRD::SETVAR I I
+
+Analog to SETENV but for local variables
+
+=item RRD::GETVAR I 
+
+Analog to GETENV but for local variables
+
 =item RRD::TIME::LAST I I
 
 This gets replaced by the last modification time of the selected RRD. The
@@ -102,16 +108,10 @@
 to allow pretty titles on graphs with times that are easier for non rrdtool
 folks to figure out than "-2weeks".
 
-=back
-
-=head2 Pass 3
-
-=over 8
-
 =item RRD::GRAPH I
 
 This tag creates the RRD graph defined in its argument and then gets
-replaced by an appropriate EIMGE tag referring to the graph.
+replaced by an appropriate EIMG tag referring to the graph.
 The B<--lazy> option in RRD graph can be used to make sure that graphs
 are only regenerated when they are out of date. The arguments
 to the B tag work as described in the B manual page.
@@ -126,7 +126,7 @@
  
 
 Note that %s stands for the filename part of the graph generated, all
-directories given in the GIF file argument will get dropped.
+directories given in the PNG file argument will get dropped.
 
 =item RRD::PRINT I
 

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdcgi.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdcgi.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdcgi.txt	Thu Jan 15 15:49:42 2004
@@ -24,7 +24,11 @@
        The argument parser uses the same semantics as you are
        used from your c shell.
 
-       PPaassss 11
+       ----ffiilltteerr
+               Assume that rrdcgi is being run as a filter and
+               not as a cgi.
+
+       KKeeyywwoorrddss
 
 
        RRD::CV _n_a_m_e
@@ -53,9 +57,6 @@
                you are using some sort of access control on the
                directory
 
-       PPaassss 22
-
-
        RRD::GOODFOR _s_e_c_o_n_d_s
                Specify the number of seconds this page should
                remain valid. This will prompt the rrdcgi to out-
@@ -76,6 +77,12 @@
                Time. Note that the values permitted to TZ depend
                on your OS.
 
+       RRD::SETVAR _v_a_r_i_a_b_l_e _v_a_l_u_e
+               Analog to SETENV but for local variables
+
+       RRD::GETVAR _v_a_r_i_a_b_l_e
+               Analog to GETENV but for local variables
+
        RRD::TIME::LAST _r_r_d_-_f_i_l_e _s_t_r_f_t_i_m_e_-_f_o_r_m_a_t
                This gets replaced by the last modification time
                of the selected RRD. The time is _s_t_r_f_t_i_m_e-formated
@@ -97,13 +104,10 @@
                graphs with times that are easier for non rrdtool
                folks to figure out than "-2weeks".
 
-       PPaassss 33
-
-
        RRD::GRAPH _r_r_d_g_r_a_p_h _a_r_g_u_m_e_n_t_s
                This tag creates the RRD graph defined in its
                argument and then gets replaced by an appropriate
-                tag referring to the graph.  The ----llaazzyy
+               
 
                Note that %s stands for the filename part of the
-               graph generated, all directories given in the GIF
+               graph generated, all directories given in the PNG
                file argument will get dropped.
 
        RRD::PRINT _n_u_m_b_e_r
@@ -203,4 +207,4 @@
 
 
 
-1.0.45                      2003-05-20                  RRDCGI(1)
+1.0.46                      2003-11-23                  RRDCGI(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdcreate.html
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdcreate.html	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdcreate.html	Thu Jan 15 15:49:42 2004
@@ -41,7 +41,7 @@
 
 
 DESCRIPTION
-The create function of the RRDtool lets you set up new
+
The create function of the RRDTool lets you set up new
 Round Robin Database (RRD) files. 
 The file is created at its final, full size and filled
 with *UNKNOWN* data.
@@ -50,7 +50,7 @@
 
 
 The name of the RRD you want to create. RRD files should end
-with the extension .rrd. However, rrdtool will accept any
+with the extension .rrd. However, RRDTool will accept any
 filename.
 
 
@@ -58,7 +58,7 @@
 
 
 Specifies the time in seconds since 1970-01-01 UTC when the first
-value should be added to the RRD. rrdtool will not accept
+value should be added to the RRD. RRDTool will not accept
 any data timed before or at the time specified.
 
 
@@ -88,7 +88,7 @@
 
 
 DST defines the Data Source Type. See the section on ``How to Measure'' below for further insight.
-The Datasource Type must be one of the following:
+The Data Source Type must be one of the following:
 
 
 GAUGE

@@ -105,7 +105,7 @@
 InOctets counter in a router. The COUNTER data source assumes that
 the counter never decreases, except when a counter overflows.  The update
 function takes the overflow into account.  The counter is stored as a
-per-second rate. When the counter overflows, RRDtool checks if the overflow happened at
+per-second rate. When the counter overflows, RRDTool checks if the overflow happened at
 the 32bit or 64bit border and acts accordingly by adding an appropriate value to the result.
 
 
@@ -141,7 +141,7 @@
 of the DS. For a traffic-COUNTER type DS this would be the max and min
 data-rate expected from the device.
 If information on minimal/maximal expected values is available,
-always set the min and/or max properties. This will help RRDtool in
+always set the min and/or max properties. This will help RRDTool in
 doing a simple sanity check on the data supplied when running update.
 
RRA:CF:xff:steps:rows

 
@@ -176,7 +176,7 @@
 
 
 The HEARTBEAT and the STEP
-Here is an explanation by Don Baarda on the inner workings of rrdtool.
+
Here is an explanation by Don Baarda on the inner workings of RRDTool.
 It may help you to sort out why all this *UNKNOWN* data is popping
 up in your databases:
 RRD gets fed samples at arbitrary times. From these it builds Primary
@@ -204,7 +204,7 @@
 require multiple samples per PDP, and if you don't get them mark the
 PDP unknown. A long heartbeat can span multiple ``steps'', which means
 it is acceptable to have multiple PDPs calculated from a single
-sample. An extreme example of this might be a ``step'' of 5mins and a
+sample. An extreme example of this might be a ``step'' of 5 minutes and a
 ``heartbeat'' of one day, in which case a single sample every day will
 result in all the PDPs for that entire day period being set to the
 same average rate. -- Don Baarda <don.baarda at baesystems.com>
@@ -218,9 +218,9 @@
 
 
 Normally you have some type of meter you can read to get the temperature.
-The temperature is not realy connected with a time. The only connection is
+The temperature is not really connected with a time. The only connection is
 that the temperature reading happened at a certain time. You can use the
-GAUGE data source type for this. RRRtool will the record your reading
+GAUGE data source type for this. RRDTool will the record your reading
 together with the time.
 
 
@@ -230,11 +230,11 @@
 Assume you have a method to count the number of messages transported by
 your mailserver in a certain amount of time, this give you data like '5
 messages in the last 65 seconds'. If you look at the count of 5 like and
-ABSOLUTE datatype you can simply update the rrd with the number 5 and the
-end time of your monitoring period. RRDtool will then record the number of
+ABSOLUTE datatype you can simply update the RRD with the number 5 and the
+end time of your monitoring period. RRDTool will then record the number of
 messages per second. If at some later stage you want to know the number of
 messages transported in a day, you can get the average messages per second
-from RRDtool for the day in question and multiply this number with the
+from RRDTool for the day in question and multiply this number with the
 number of seconds in a day. Because all math is run with Doubles, the
 precision should be acceptable.
 
@@ -242,10 +242,10 @@
 It's always a Rate

 
 
-RRDtool stores rates in amount/second for COUNTER, DERIVE and ABSOLUTE data.
+RRDTool stores rates in amount/second for COUNTER, DERIVE and ABSOLUTE data.
 When you plot the data, you will get on the y axis amount/second which you
 might be tempted to convert to absolute amount volume by multiplying by the
-delta-time between the points. RRDtool plots continuous data, and as such is
+delta-time between the points. RRDTool plots continuous data, and as such is
 not appropriate for plotting absolute volumes as for example ``total bytes''
 sent and received in a router. What you probably want is plot rates that you
 can scale to for example bytes/hour or plot volumes with another tool that

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdcreate.pod
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdcreate.pod	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdcreate.pod	Thu Jan 15 15:49:42 2004
@@ -14,7 +14,7 @@
 
 =head1 DESCRIPTION
 
-The create function of the RRDtool lets you set up new
+The create function of the RRDTool lets you set up new
 Round Robin Database (B) files. 
 The file is created at its final, full size and filled
 with I<*UNKNOWN*> data.
@@ -24,13 +24,13 @@
 =item I
 
 The name of the B you want to create. B files should end
-with the extension F<.rrd>. However, B will accept any
+with the extension F<.rrd>. However, B will accept any
 filename.
 
 =item B<--start>|B<-b> I (default: now - 10s)
 
 Specifies the time in seconds since 1970-01-01 UTC when the first
-value should be added to the B. B will not accept
+value should be added to the B. B will not accept
 any data timed before or at the time specified.
 
 See also AT-STYLE TIME SPECIFICATION section in the
@@ -53,7 +53,7 @@
 the characters [a-zA-Z0-9_].
 
 I defines the Data Source Type. See the section on "How to Measure" below for further insight.
-The Datasource Type must be one of the following:
+The Data Source Type must be one of the following:
 
 =over 4
 
@@ -68,7 +68,7 @@
 InOctets counter in a router. The B data source assumes that
 the counter never decreases, except when a counter overflows.  The update
 function takes the overflow into account.  The counter is stored as a
-per-second rate. When the counter overflows, RRDtool checks if the overflow happened at
+per-second rate. When the counter overflows, RRDTool checks if the overflow happened at
 the 32bit or 64bit border and acts accordingly by adding an appropriate value to the result.
 
 =item B
@@ -103,7 +103,7 @@
 data-rate expected from the device.
 
 I
 
 =item BIB<:>IB<:>IB<:>I
@@ -132,7 +132,7 @@
 
 =head1 The HEARTBEAT and the STEP
 
-Here is an explanation by Don Baarda on the inner workings of rrdtool.
+Here is an explanation by Don Baarda on the inner workings of RRDTool.
 It may help you to sort out why all this *UNKNOWN* data is popping
 up in your databases:
 
@@ -164,7 +164,7 @@
 require multiple samples per PDP, and if you don't get them mark the
 PDP unknown. A long heartbeat can span multiple "steps", which means
 it is acceptable to have multiple PDPs calculated from a single
-sample. An extreme example of this might be a "step" of 5mins and a
+sample. An extreme example of this might be a "step" of 5 minutes and a
 "heartbeat" of one day, in which case a single sample every day will
 result in all the PDPs for that entire day period being set to the
 same average rate. I<-- Don Baarda Edon.baarda at baesystems.comE>
@@ -180,9 +180,9 @@
 =item Temperature
 
 Normally you have some type of meter you can read to get the temperature.
-The temperature is not realy connected with a time. The only connection is
+The temperature is not really connected with a time. The only connection is
 that the temperature reading happened at a certain time. You can use the
-B data source type for this. RRRtool will the record your reading
+B data source type for this. RRDTool will the record your reading
 together with the time.
 
 =item Mail Messages
@@ -190,20 +190,20 @@
 Assume you have a method to count the number of messages transported by
 your mailserver in a certain amount of time, this give you data like '5
 messages in the last 65 seconds'. If you look at the count of 5 like and
-B datatype you can simply update the rrd with the number 5 and the
-end time of your monitoring period. RRDtool will then record the number of
+B datatype you can simply update the RRD with the number 5 and the
+end time of your monitoring period. RRDTool will then record the number of
 messages per second. If at some later stage you want to know the number of
 messages transported in a day, you can get the average messages per second
-from RRDtool for the day in question and multiply this number with the
+from RRDTool for the day in question and multiply this number with the
 number of seconds in a day. Because all math is run with Doubles, the
 precision should be acceptable.
 
 =item It's always a Rate
 
-RRDtool stores rates in amount/second for COUNTER, DERIVE and ABSOLUTE data.
+RRDTool stores rates in amount/second for COUNTER, DERIVE and ABSOLUTE data.
 When you plot the data, you will get on the y axis amount/second which you
 might be tempted to convert to absolute amount volume by multiplying by the
-delta-time between the points. RRDtool plots continuous data, and as such is
+delta-time between the points. RRDTool plots continuous data, and as such is
 not appropriate for plotting absolute volumes as for example "total bytes"
 sent and received in a router. What you probably want is plot rates that you
 can scale to for example bytes/hour or plot volumes with another tool that

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdcreate.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdcreate.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdcreate.txt	Thu Jan 15 15:49:42 2004
@@ -11,19 +11,19 @@
        [RRRRAA::_C_F::_x_f_f::_s_t_e_p_s::_r_o_w_s]
 
 DDEESSCCRRIIPPTTIIOONN
-       The create function of the RRDtool lets you set up new
+       The create function of the RRDTool lets you set up new
        Round Robin Database (RRRRDD) files.  The file is created at
        its final, full size and filled with _*_U_N_K_N_O_W_N_* data.
 
        _f_i_l_e_n_a_m_e
                The name of the RRRRDD you want to create. RRRRDD files
-               should end with the extension _._r_r_d. However, rrrrdd--
-               ttooooll will accept any filename.
+               should end with the extension _._r_r_d. However, RRRRDD--
+               TTooooll will accept any filename.
 
        ----ssttaarrtt|--bb _s_t_a_r_t _t_i_m_e (default: now - 10s)
                Specifies the time in seconds since 1970-01-01 UTC
                when the first value should be added to the RRRRDD.
-               rrrrddttooooll will not accept any data timed before or
+               RRRRDDTTooooll will not accept any data timed before or
                at the time specified.
 
                See also AT-STYLE TIME SPECIFICATION section in
@@ -49,7 +49,7 @@
 
                _D_S_T defines the Data Source Type. See the section
                on "How to Measure" below for further insight.
-               The Datasource Type must be one of the following:
+               The Data Source Type must be one of the following:
 
                GGAAUUGGEE
                    is for things like temperatures or number of
@@ -62,7 +62,7 @@
                    decreases, except when a counter overflows.
                    The update function takes the overflow into
                    account.  The counter is stored as a per-sec-
-                   ond rate. When the counter overflows, RRDtool
+                   ond rate. When the counter overflows, RRDTool
                    checks if the overflow happened at the 32bit
                    or 64bit border and acts accordingly by adding
                    an appropriate value to the result.
@@ -106,7 +106,7 @@
 
                _I_f _i_n_f_o_r_m_a_t_i_o_n _o_n _m_i_n_i_m_a_l_/_m_a_x_i_m_a_l _e_x_p_e_c_t_e_d _v_a_l_u_e_s
                _i_s _a_v_a_i_l_a_b_l_e_, _a_l_w_a_y_s _s_e_t _t_h_e _m_i_n _a_n_d_/_o_r _m_a_x _p_r_o_p_-
-               _e_r_t_i_e_s_. _T_h_i_s _w_i_l_l _h_e_l_p _R_R_D_t_o_o_l _i_n _d_o_i_n_g _a _s_i_m_p_l_e
+               _e_r_t_i_e_s_. _T_h_i_s _w_i_l_l _h_e_l_p _R_R_D_T_o_o_l _i_n _d_o_i_n_g _a _s_i_m_p_l_e
                _s_a_n_i_t_y _c_h_e_c_k _o_n _t_h_e _d_a_t_a _s_u_p_p_l_i_e_d _w_h_e_n _r_u_n_n_i_n_g
                _u_p_d_a_t_e_.
 
@@ -139,7 +139,7 @@
 
 TThhee HHEEAARRTTBBEEAATT aanndd tthhee SSTTEEPP
        Here is an explanation by Don Baarda on the inner workings
-       of rrdtool.  It may help you to sort out why all this
+       of RRDTool.  It may help you to sort out why all this
        *UNKNOWN* data is popping up in your databases:
 
        RRD gets fed samples at arbitrary times. From these it
@@ -174,9 +174,9 @@
        and if you don't get them mark the PDP unknown. A long
        heartbeat can span multiple "steps", which means it is
        acceptable to have multiple PDPs calculated from a single
-       sample. An extreme example of this might be a "step" of
-       5mins and a "heartbeat" of one day, in which case a single
-       sample every day will result in all the PDPs for that
+       sample. An extreme example of this might be a "step" of 5
+       minutes and a "heartbeat" of one day, in which case a sin-
+       gle sample every day will result in all the PDPs for that
        entire day period being set to the same average rate. _-_-
        _D_o_n _B_a_a_r_d_a _<_d_o_n_._b_a_a_r_d_a_@_b_a_e_s_y_s_t_e_m_s_._c_o_m_>
 
@@ -185,10 +185,10 @@
 
        Temperature
            Normally you have some type of meter you can read to
-           get the temperature.  The temperature is not realy
+           get the temperature.  The temperature is not really
            connected with a time. The only connection is that the
            temperature reading happened at a certain time. You
-           can use the GGAAUUGGEE data source type for this. RRRtool
+           can use the GGAAUUGGEE data source type for this. RRDTool
            will the record your reading together with the time.
 
        Mail Messages
@@ -197,23 +197,23 @@
            amount of time, this give you data like '5 messages in
            the last 65 seconds'. If you look at the count of 5
            like and AABBSSOOLLUUTTEE datatype you can simply update the
-           rrd with the number 5 and the end time of your moni-
-           toring period. RRDtool will then record the number of
+           RRD with the number 5 and the end time of your moni-
+           toring period. RRDTool will then record the number of
            messages per second. If at some later stage you want
            to know the number of messages transported in a day,
            you can get the average messages per second from RRD-
-           tool for the day in question and multiply this number
+           Tool for the day in question and multiply this number
            with the number of seconds in a day. Because all math
            is run with Doubles, the precision should be accept-
            able.
 
        It's always a Rate
-           RRDtool stores rates in amount/second for COUNTER,
+           RRDTool stores rates in amount/second for COUNTER,
            DERIVE and ABSOLUTE data.  When you plot the data, you
            will get on the y axis amount/second which you might
            be tempted to convert to absolute amount volume by
            multiplying by the delta-time between the points. RRD-
-           tool plots continuous data, and as such is not appro-
+           Tool plots continuous data, and as such is not appro-
            priate for plotting absolute volumes as for example
            "total bytes" sent and received in a router. What you
            probably want is plot rates that you can scale to for
@@ -248,4 +248,4 @@
 
 
 
-1.0.45                      2002-12-20               RRDCREATE(1)
+1.0.46                      2003-09-14               RRDCREATE(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrddump.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrddump.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrddump.txt	Thu Jan 15 15:49:42 2004
@@ -24,4 +24,4 @@
 
 
 
-1.0.45                      2002-02-26                 RRDDUMP(1)
+1.0.46                      2002-02-26                 RRDDUMP(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdfetch.html
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdfetch.html	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdfetch.html	Thu Jan 15 15:49:42 2004
@@ -33,7 +33,7 @@
 
 
 NAME
-rrdtool fetch - fetch data from an rrd.
+rrdtool fetch - fetch data from an RRD.
 PDF version.

 
 
@@ -94,7 +94,7 @@
 
 
 RESOLUTION INTERVAL
-In order to get rrdtool to fetch anything other than the finest resolution RRA 
+
In order to get RRDTool to fetch anything other than the finest resolution RRA 
 both the start and end time must be specified on boundaries that are 
 multiples of the wanted resolution. Consider the following example:
 @@ -130,14 +130,14 @@
   TIME=$(date +%s); RRDRES=900; rrdtool fetch subdata.rrd AVERAGE -r $RRDRES \
  -e $(echo $(($TIME/$RRDRES*$RRDRES))) -s e-1h
-Or in perl:
+Or in Perl:
   perl -e '$ctime = time; $rrdres = 900; system "rrdtool fetch subdata.rrd AVERAGE \
  -r $rrdres -e @{[int($ctime/$rrdres)*$rrdres]} -s e-1h"'
 
 
 AT-STYLE TIME SPECIFICATION
-Apart from the traditional Seconds since epoch, rrdtool does also
+
Apart from the traditional Seconds since epoch, RRDTool does also
 understand at-style time specification.  The specification is called
 ``at-style'' after Unix command at(1) that has moderately complex ways
 to specify time to run your job at.  The at-style specification
@@ -170,7 +170,7 @@
 reference. Now refers to the current moment (and is also a default
 time reference). Start (end) can be used to specify time
 relative to the start (end) time for those tools that use these
-categories (rrdfetch, rrdgraph).
+categories (rrdfetch, the rrdgraph manpage).
 Month and weekday names can be used in their naturally abbreviated form
 (e.g., Dec for December, Sun for Sunday, etc.). The words now,
 start, end can be abbreviated to n, s, e.

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdfetch.pod
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdfetch.pod	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdfetch.pod	Thu Jan 15 15:49:42 2004
@@ -1,6 +1,6 @@
 =head1 NAME
 
-rrdtool fetch - fetch data from an rrd.
+rrdtool fetch - fetch data from an RRD.
 
 =for html PDF version.
 
@@ -54,7 +54,7 @@
 
 =head2 RESOLUTION INTERVAL
 
-In order to get rrdtool to fetch anything other than the finest resolution RRA 
+In order to get RRDTool to fetch anything other than the finest resolution RRA 
 B the start and end time must be specified on boundaries that are 
 multiples of the wanted resolution. Consider the following example:
 
@@ -102,7 +102,7 @@
  TIME=$(date +%s); RRDRES=900; rrdtool fetch subdata.rrd AVERAGE -r $RRDRES \
  -e $(echo $(($TIME/$RRDRES*$RRDRES))) -s e-1h
 
-Or in perl:
+Or in Perl:
 
  perl -e '$ctime = time; $rrdres = 900; system "rrdtool fetch subdata.rrd AVERAGE \
  -r $rrdres -e @{[int($ctime/$rrdres)*$rrdres]} -s e-1h"'
@@ -110,7 +110,7 @@
 
 =head2 AT-STYLE TIME SPECIFICATION
 
-Apart from the traditional I, rrdtool does also
+Apart from the traditional I, RRDTool does also
 understand at-style time specification.  The specification is called
 "at-style" after Unix command at(1) that has moderately complex ways
 to specify time to run your job at.  The at-style specification
@@ -148,7 +148,7 @@
 reference. B refers to the current moment (and is also a default
 time reference). B (B) can be used to specify time
 relative to the start (end) time for those tools that use these
-categories (rrdfetch, rrdgraph).
+categories (B, L).
 
 Month and weekday names can be used in their naturally abbreviated form
 (e.g., Dec for December, Sun for Sunday, etc.). The words B,

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdfetch.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdfetch.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdfetch.txt	Thu Jan 15 15:49:42 2004
@@ -3,7 +3,7 @@
 
 
 NNAAMMEE
-       rrdtool fetch - fetch data from an rrd.
+       rrdtool fetch - fetch data from an RRD.
 
 SSYYNNOOPPSSIISS
        rrrrddttooooll ffeettcchh _f_i_l_e_n_a_m_e _C_F [----rreessoolluuttiioonn|--rr _r_e_s_o_l_u_t_i_o_n]
@@ -49,7 +49,7 @@
 
        RREESSOOLLUUTTIIOONN IINNTTEERRVVAALL
 
-       In order to get rrdtool to fetch anything other than the
+       In order to get RRDTool to fetch anything other than the
        finest resolution RRA bbootthh the start and end time must be
        specified on boundaries that are multiples of the wanted
        resolution. Consider the following example:
@@ -92,14 +92,14 @@
         TIME=$(date +%s); RRDRES=900; rrdtool fetch subdata.rrd AVERAGE -r $RRDRES \
         -e $(echo $(($TIME/$RRDRES*$RRDRES))) -s e-1h
 
-       Or in perl:
+       Or in Perl:
 
         perl -e '$ctime = time; $rrdres = 900; system "rrdtool fetch subdata.rrd AVERAGE \
         -r $rrdres -e @{[int($ctime/$rrdres)*$rrdres]} -s e-1h"'
 
        AATT--SSTTYYLLEE TTIIMMEE SSPPEECCIIFFIICCAATTIIOONN
 
-       Apart from the traditional _S_e_c_o_n_d_s _s_i_n_c_e _e_p_o_c_h, rrdtool
+       Apart from the traditional _S_e_c_o_n_d_s _s_i_n_c_e _e_p_o_c_h, RRDTool
        does also understand at-style time specification.  The
        specification is called "at-style" after Unix command
        _a_t(1) that has moderately complex ways to specify time to
@@ -140,7 +140,7 @@
        reference. NNooww refers to the current moment (and is also a
        default time reference). SSttaarrtt (eenndd) can be used to spec-
        ify time relative to the start (end) time for those tools
-       that use these categories (rrdfetch, rrdgraph).
+       that use these categories (rrrrddffeettcchh, rrdgraph).
 
        Month and weekday names can be used in their naturally
        abbreviated form (e.g., Dec for December, Sun for Sunday,
@@ -249,4 +249,4 @@
 
 
 
-1.0.45                      2003-04-16                RRDFETCH(1)
+1.0.46                      2003-09-14                RRDFETCH(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdgraph.html
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdgraph.html	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdgraph.html	Thu Jan 15 15:49:42 2004
@@ -52,6 +52,7 @@
 [-M|--alt-autoscale-max]
 [-N|--no-minor]
 [-X|--units-exponent] value]>
+[-L|--units-length] value]>
 [-v|--vertical-label text]
 [-w|--width pixels]
 [-h|--height pixels] 
@@ -92,9 +93,9 @@
 filename

 
 
-The name of the graph to generate. Since rrdtool outputs
+The name of the graph to generate. Since RRDTool outputs
 GIFs and PNGs, it's recommended that the filename end in either
-.gif or .png.  rrdtool does not enforce this, however.
+.gif or .png.  RRDTool does not enforce this, however.
 If the  filename is set to '-' the image file will be written
 to standard out.  All other output will get suppressed.
 
@@ -171,8 +172,8 @@
 you make sure that this happens.
 
 
-If you want to alter the genertated text to another language, use the
-LC_TIME environment variable to set the locale you prefere prior to calling
+
If you want to alter the generated text to another language, use the
+LC_TIME environment variable to set the locale you prefer prior to calling
 the graph function.
 
 
@@ -199,7 +200,7 @@
 --no-minor

 
 
-Turn off the minor grid lines.  This is partcularly useful for small 
+Turn off the minor grid lines.  This is particularly useful for small 
 graphs which can be cluttered with the minor grid lines. (contributed
 by Travis Brown)
 
@@ -207,7 +208,7 @@
 -R|--alt-y-mrtg

 
 
-Y grid placed on graph Y range mimmics mrtg's (rateup-generated) graphs.
+Y grid placed on graph Y range mimics MRTG's (rateup-generated) graphs.
 Currently axis is split into 4 parts, just as rateup does.
 
 
@@ -248,6 +249,13 @@
 of 0 to prevent any scaling of the y-axis values.
 
 
+-L|--units-length value (default 9 characters)

+
+
+This sets the character width on the left side of the graph for y-axis
+values.
+
+
 -v|--vertical-label text

 
 
@@ -298,7 +306,7 @@
 
-a|--imgformat GIF|PNG|GD (default: GIF)

 
 
-Allows you to produce PNG or GD output from rrdtool.
+Allows you to produce PNG or GD output from RRDTool.
 
 
 -B|--background value

@@ -335,7 +343,7 @@
 

 Defines the value normally located at the upper border of the
 graph. If the graph contains higher values, the upper border will
-move upwards to accomodate these values as well.
+move upwards to accommodate these values as well.
 
 
 If you want to define an upper-limit which will not move in any
@@ -354,7 +362,7 @@
 
-r|--rigid

 
 
-rigid boundaries mode.  Normally rrdgraph will automatically expand the
+rigid boundaries mode.  Normally rrdgraph will automatically expand the
 lower and upper limit if the graph contains a value outside the valid
 range. With the r option you can disable this behavior
 
@@ -398,9 +406,9 @@
 -S|--step value (default automatic)

 
 
-By default rrdgraph calculates the width of one pixel in the time domain and
+By default rrdgraph calculates the width of one pixel in the time domain and
 tries to get data at that resolution from the RRD. With this switch you can
-override this behaviour. If you want rrdgraph to get data at 1 hour
+override this behavior. If you want rrdgraph to get data at 1 hour
 resolution from the RRD, then you can set the step to 3600 seconds. Note,
 that a step smaller than 1 pixel will be silently ignored.
 
@@ -573,7 +581,7 @@
 
 
 Note that the timezone offset is always calculated for the time the
-current sample was taken at. It has nuthing todo with the time you are
+current sample was taken at. It has nothing to do with the time you are
 doing the calculation.
 
 
@@ -670,7 +678,7 @@
 the first place ;)
 
 
-Note, that when you STACK onto *UNKNOWN* data, rrdtool will not draw
+
Note, that when you STACK onto *UNKNOWN* data, RRDTool will not draw
 any graphics ... *UNKNOWN* is not zero ... if you want it to zero
 then you might want to use a CDEF argument with IF and UN functions to
 turn *UNKNOWN* into zero ...
@@ -686,7 +694,7 @@
 In a ':' in a legend argument will mark the end of the legend. To
 enter a ':' into a legend, the colon must be escaped with a backslash '\:'.
 Beware, that many environments look for backslashes themselves, so it may
-be necessary to write two backslashes so that one is passed onto rrd_graph.
+be necessary to write two backslashes so that one is passed onto rrdgraph.
 
 
 String Formatting
@@ -699,15 +707,15 @@
 example showing how to use centered formating.
 Normally there are two space characters inserted between every two items
 printed into the graph. The space following a string can be suppressed by
-putting a \g at the end of the string. The \g also squshes any space
+putting a \g at the end of the string. The \g also squashes any space
 inside the string if it is at the very end of the string. This can be used
-in connection with %s to supress empty unit strings.
+in connection with %s to suppress empty unit strings.
   GPRINT:a:MAX:%lf%s\g
 A special case is COMMENT:\s this inserts some additional vertical space
 before placing the next row of legends.
 When text has to be formated without special instructions from your side,
-rrdtool will automatically justify the text as soon as one string goes over
+RRDTool will automatically justify the text as soon as one string goes over
 the right edge. If you want to prevent the justification without forcing a
 newline, you can use the special tag \J at the end of the string to
 disable the auto justification.
@@ -715,7 +723,7 @@
 
 
 NOTE on Return Values
-Whenever rrd_graph gets called, it prints a line telling the size of
+
Whenever rrdgraph gets called, it prints a line telling the size of
 the gif it has just created to STDOUT. This line looks like this: XSIZExYSIZE.
 
 
@@ -787,7 +795,7 @@
 not least, overlay everything with eye-hurting red
 to signal any unknown data.
 Note that this example assumes that your data is in the positive half of the y-axis
-otherwhise you would would have to add NEGINF in order to extend the coverage
+otherwise you would have to add NEGINF in order to extend the coverage
 of the rea to whole graph.
 
 

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdgraph.pod
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdgraph.pod	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdgraph.pod	Thu Jan 15 15:49:42 2004
@@ -17,6 +17,7 @@
 S<[B<-M>|B<--alt-autoscale-max>]>
 S<[B<-N>|B<--no-minor>]>
 S<[B<-X>|B<--units-exponent>]> I]>
+S<[B<-L>|B<--units-length>]> I]>
 S<[B<-v>|B<--vertical-label> I]>
 S<[B<-w>|B<--width> I]>
 S<[B<-h>|B<--height> I]> 
@@ -57,9 +58,9 @@
 
 =item I 
 
-The name of the graph to generate. Since B outputs
+The name of the graph to generate. Since B outputs
 GIFs and PNGs, it's recommended that the filename end in either
-F<.gif> or F<.png>.  B does not enforce this, however.
+F<.gif> or F<.png>.  B does not enforce this, however.
 If the  I is set to '-' the image file will be written
 to standard out.  All other output will get suppressed.
 
@@ -119,8 +120,8 @@
 at noon. By defining a precision of 24 hours or rather 86400 seconds,
 you make sure that this happens.
 
-If you want to alter the genertated text to another language, use the
-LC_TIME environment variable to set the locale you prefere prior to calling
+If you want to alter the generated text to another language, use the
+LC_TIME environment variable to set the locale you prefer prior to calling
 the graph function.
 
 =item B<-y>|B<--y-grid> I:I (default autoconfigure)
@@ -140,14 +141,14 @@
 
 =item B<--no-minor>
 
-Turn off the minor grid lines.  This is partcularly useful for small 
+Turn off the minor grid lines.  This is particularly useful for small 
 graphs which can be cluttered with the minor grid lines. (contributed
 by Travis Brown)
 
 
 =item B<-R>|B<--alt-y-mrtg>
 
-Y grid placed on graph Y range mimmics mrtg's (rateup-generated) graphs.
+Y grid placed on graph Y range mimics MRTG's (rateup-generated) graphs.
 Currently axis is split into 4 parts, just as rateup does.
 
 =item B<-A>|B<--alt-autoscale>
@@ -181,6 +182,11 @@
 display the y-axis values in u (Micro, 10e-6, millionths).  Use a value
 of 0 to prevent any scaling of the y-axis values.
 
+=item B<-L>|B<--units-length> I (default 9 characters)
+
+This sets the character width on the left side of the graph for y-axis
+values.
+
 =item B<-v>|B<--vertical-label> I
 
 vertical label on the left side of the graph. This is normally used to
@@ -218,7 +224,7 @@
 
 =item B<-a>|B<--imgformat> B|B|B (default: GIF)
 
-Allows you to produce PNG or GD output from rrdtool. 
+Allows you to produce PNG or GD output from RRDTool. 
 
 =item B<-B>|B<--background> I
 
@@ -245,7 +251,7 @@
 
 Defines the value normally located at the upper border of the
 graph. If the graph contains higher values, the upper border will
-move upwards to accomodate these values as well.
+move upwards to accommodate these values as well.
 
 If you want to define an upper-limit which will not move in any
 event you have to set the B<--rigid> option as well.
@@ -259,7 +265,7 @@
 
 =item B<-r>|B<--rigid>
 
-rigid boundaries mode.  Normally rrdgraph will automatically expand the
+rigid boundaries mode.  Normally B will automatically expand the
 lower and upper limit if the graph contains a value outside the valid
 range. With the r option you can disable this behavior
 
@@ -291,9 +297,9 @@
 
 =item B<-S>|B<--step> I (default automatic)
 
-By default rrdgraph calculates the width of one pixel in the time domain and
+By default B calculates the width of one pixel in the time domain and
 tries to get data at that resolution from the RRD. With this switch you can
-override this behaviour. If you want rrdgraph to get data at 1 hour
+override this behavior. If you want B to get data at 1 hour
 resolution from the RRD, then you can set the step to 3600 seconds. Note,
 that a step smaller than 1 pixel will be silently ignored.
 
@@ -428,7 +434,7 @@
 hours ahead of UTC.
 
 Note that the timezone offset is always calculated for the time the
-current sample was taken at. It has nuthing todo with the time you are
+current sample was taken at. It has nothing to do with the time you are
 doing the calculation.
 
 =back
@@ -513,7 +519,7 @@
 B or B -- you need something to stack something onto in
 the first place ;) 
 
-Note, that when you STACK onto *UNKNOWN* data, rrdtool will not draw
+Note, that when you STACK onto *UNKNOWN* data, RRDTool will not draw
 any graphics ... *UNKNOWN* is not zero ... if you want it to zero
 then you might want to use a CDEF argument with IF and UN functions to
 turn *UNKNOWN* into zero ...
@@ -527,7 +533,7 @@
 In a ':' in a I argument will mark the end of the legend. To
 enter a ':' into a legend, the colon must be escaped with a backslash '\:'.
 Beware, that many environments look for backslashes themselves, so it may
-be necessary to write two backslashes so that one is passed onto rrd_graph.
+be necessary to write two backslashes so that one is passed onto B.
 
 =head2 String Formatting
 
@@ -542,9 +548,9 @@
 
 Normally there are two space characters inserted between every two items
 printed into the graph. The space following a string can be suppressed by
-putting a B<\g> at the end of the string. The B<\g> also squshes any space
+putting a B<\g> at the end of the string. The B<\g> also squashes any space
 inside the string if it is at the very end of the string. This can be used
-in connection with B<%s> to supress empty unit strings.
+in connection with B<%s> to suppress empty unit strings.
 
  GPRINT:a:MAX:%lf%s\g
 
@@ -553,14 +559,14 @@
 before placing the next row of legends.
 
 When text has to be formated without special instructions from your side,
-rrdtool will automatically justify the text as soon as one string goes over
+RRDTool will automatically justify the text as soon as one string goes over
 the right edge. If you want to prevent the justification without forcing a
 newline, you can use the special tag B<\J> at the end of the string to
 disable the auto justification.
 
 =head1 NOTE on Return Values
 
-Whenever rrd_graph gets called, it prints a line telling the size of
+Whenever B gets called, it prints a line telling the size of
 the gif it has just created to STDOUT. This line looks like this: XSIZExYSIZE.
 
 =head1 EXAMPLE 1
@@ -633,7 +639,7 @@
 to signal any unknown data.
 
 Note that this example assumes that your data is in the positive half of the y-axis
-otherwhise you would would have to add NEGINF in order to extend the coverage
+otherwise you would have to add NEGINF in order to extend the coverage
 of the rea to whole graph.
 
 =head1 AUTHOR

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdgraph.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdgraph.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdgraph.txt	Thu Jan 15 15:49:42 2004
@@ -12,12 +12,12 @@
        [--yy|----yy--ggrriidd _y_-_a_x_i_s _g_r_i_d _a_n_d _l_a_b_e_l] [--YY|----aalltt--yy--ggrriidd]
        [--RR|----aalltt--yy--mmrrttgg] [--AA|----aalltt--aauuttoossccaallee]
        [--MM|----aalltt--aauuttoossccaallee--mmaaxx] [--NN|----nnoo--mmiinnoorr] [--XX|----uunniittss--eexxppoo--
-       nneenntt] _v_a_l_u_e]> [--vv|----vveerrttiiccaall--llaabbeell _t_e_x_t] [--ww|----wwiiddtthh _p_i_x_-
-       _e_l_s] [--hh|----hheeiigghhtt _p_i_x_e_l_s] [--ii|----iinntteerrllaacceedd]
-       [--ff|----iimmggiinnffoo _f_o_r_m_a_t_s_t_r_i_n_g] [--aa|----iimmggffoorrmmaatt GGIIFF|PPNNGG|GGDD]
-       [--BB|----bbaacckkggrroouunndd _v_a_l_u_e] [--OO|----oovveerrllaayy _v_a_l_u_e]
-       [--UU|----uunniitt _v_a_l_u_e] [--zz|----llaazzyy] [--oo|----llooggaarriitthhmmiicc]
-       [--uu|----uuppppeerr--lliimmiitt _v_a_l_u_e] [--ll|----lloowweerr--lliimmiitt _v_a_l_u_e]
+       nneenntt] _v_a_l_u_e]> [--LL|----uunniittss--lleennggtthh] _v_a_l_u_e]> [--vv|----vveerrttii--
+       ccaall--llaabbeell _t_e_x_t] [--ww|----wwiiddtthh _p_i_x_e_l_s] [--hh|----hheeiigghhtt _p_i_x_e_l_s]
+       [--ii|----iinntteerrllaacceedd] [--ff|----iimmggiinnffoo _f_o_r_m_a_t_s_t_r_i_n_g] [--aa|----iimmgg--
+       ffoorrmmaatt GGIIFF|PPNNGG|GGDD] [--BB|----bbaacckkggrroouunndd _v_a_l_u_e] [--OO|----oovveerr--
+       llaayy _v_a_l_u_e] [--UU|----uunniitt _v_a_l_u_e] [--zz|----llaazzyy] [--oo|----llooggaarriitthh--
+       mmiicc] [--uu|----uuppppeerr--lliimmiitt _v_a_l_u_e] [--ll|----lloowweerr--lliimmiitt _v_a_l_u_e]
        [--gg|----nnoo--lleeggeenndd] [--rr|----rriiggiidd] [--SS|----sstteepp _v_a_l_u_e]
        [--bb|----bbaassee _v_a_l_u_e] [--cc|----ccoolloorr _C_O_L_O_R_T_A_G##_r_r_g_g_b_b]
        [--tt|----ttiittllee _t_i_t_l_e] [DDEEFF::_v_n_a_m_e==_r_r_d::_d_s_-_n_a_m_e::_C_F]
@@ -35,9 +35,9 @@
        cal reports.
 
        _f_i_l_e_n_a_m_e
-           The name of the graph to generate. Since rrrrddttooooll out-
+           The name of the graph to generate. Since RRRRDDTTooooll out-
            puts GIFs and PNGs, it's recommended that the filename
-           end in either _._g_i_f or _._p_n_g.  rrrrddttooooll does not enforce
+           end in either _._g_i_f or _._p_n_g.  RRRRDDTTooooll does not enforce
            this, however.  If the  _f_i_l_e_n_a_m_e is set to '-' the
            image file will be written to standard out.  All other
            output will get suppressed.
@@ -105,10 +105,10 @@
            hours or rather 86400 seconds, you make sure that this
            happens.
 
-           If you want to alter the genertated text to another
+           If you want to alter the generated text to another
            language, use the LC_TIME environment variable to set
-           the locale you prefere prior to calling the graph
-           function.
+           the locale you prefer prior to calling the graph func-
+           tion.
 
        --yy|----yy--ggrriidd _g_r_i_d _s_t_e_p:_l_a_b_e_l _f_a_c_t_o_r (default autoconfigure)
            Makes vertical grid lines appear at _g_r_i_d _s_t_e_p inter-
@@ -127,12 +127,12 @@
            10 units.  (contributed by Sasha Mikheev)
 
        ----nnoo--mmiinnoorr
-           Turn off the minor grid lines.  This is partcularly
+           Turn off the minor grid lines.  This is particularly
            useful for small graphs which can be cluttered with
            the minor grid lines. (contributed by Travis Brown)
 
        --RR|----aalltt--yy--mmrrttgg
-           Y grid placed on graph Y range mimmics mrtg's
+           Y grid placed on graph Y range mimics MRTG's
            (rateup-generated) graphs.  Currently axis is split
            into 4 parts, just as rateup does.
 
@@ -171,6 +171,10 @@
            lionths).  Use a value of 0 to prevent any scaling of
            the y-axis values.
 
+       --LL|----uunniittss--lleennggtthh _v_a_l_u_e (default 9 characters)
+           This sets the character width on the left side of the
+           graph for y-axis values.
+
        --vv|----vveerrttiiccaall--llaabbeell _t_e_x_t
            vertical label on the left side of the graph. This is
            normally used to specify the units used.
@@ -204,7 +208,7 @@
             --imginfo ''
 
        --aa|----iimmggffoorrmmaatt GGIIFF|PPNNGG|GGDD (default: GIF)
-           Allows you to produce PNG or GD output from rrdtool.
+           Allows you to produce PNG or GD output from RRDTool.
 
        --BB|----bbaacckkggrroouunndd _v_a_l_u_e
            You could use image in (currently only) GD format for
@@ -229,7 +233,7 @@
        --uu|----uuppppeerr--lliimmiitt _v_a_l_u_e (default autoconfigure)
            Defines the value normally located at the upper border
            of the graph. If the graph contains higher values, the
-           upper border will move upwards to accomodate these
+           upper border will move upwards to accommodate these
            values as well.
 
            If you want to define an upper-limit which will not
@@ -244,7 +248,7 @@
            expand graphs down.
 
        --rr|----rriiggiidd
-           rigid boundaries mode.  Normally rrdgraph will auto-
+           rigid boundaries mode.  Normally rrrrddggrraapphh will auto-
            matically expand the lower and upper limit if the
            graph contains a value outside the valid range. With
            the r option you can disable this behavior
@@ -261,8 +265,8 @@
        --cc|----ccoolloorr _C_O_L_O_R_T_A_G##_r_r_g_g_b_b (default colors)
            override the colors for the standard elements of the
            graph. The _C_O_L_O_R_T_A_G must be one of the following sym-
-           bolic names: BBAACCKK ground, CCAANNVVAASS, SSHHAADDEEAA left/top
-           border, SSHHAADDEEBB right/bottom border, GGRRIIDD, MMGGRRIIDD major
+           bolic names: BBAACCKK ground, CCAANNVVAASS, SSHHAADDEEAA left/top bor-
+           der, SSHHAADDEEBB right/bottom border, GGRRIIDD, MMGGRRIIDD major
            grid, FFOONNTT, FFRRAAMMEE and axis of the graph or AARRRROOWW. This
            option can be called multiple times to set several
            colors.
@@ -274,10 +278,10 @@
            Define a title to be written into the graph
 
        --SS|----sstteepp _v_a_l_u_e (default automatic)
-           By default rrdgraph calculates the width of one pixel
+           By default rrrrddggrraapphh calculates the width of one pixel
            in the time domain and tries to get data at that reso-
            lution from the RRD. With this switch you can override
-           this behaviour. If you want rrdgraph to get data at 1
+           this behavior. If you want rrrrddggrraapphh to get data at 1
            hour resolution from the RRD, then you can set the
            step to 3600 seconds. Note, that a step smaller than 1
            pixel will be silently ignored.
@@ -416,7 +420,7 @@
 
                Note that the timezone offset is always calculated
                for the time the current sample was taken at. It
-               has nuthing todo with the time you are doing the
+               has nothing to do with the time you are doing the
                calculation.
 
            Please note that you may only use _v_n_a_m_e variables that
@@ -501,7 +505,7 @@
            AARREEAA or LLIINNEE?? -- you need something to stack something
            onto in the first place ;)
 
-           Note, that when you STACK onto *UNKNOWN* data, rrdtool
+           Note, that when you STACK onto *UNKNOWN* data, RRDTool
            will not draw any graphics ... *UNKNOWN* is not zero
            ... if you want it to zero then you might want to use
            a CDEF argument with IF and UN functions to turn
@@ -515,7 +519,7 @@
        escaped with a backslash '\:'.  Beware, that many environ-
        ments look for backslashes themselves, so it may be neces-
        sary to write two backslashes so that one is passed onto
-       rrd_graph.
+       rrrrddggrraapphh.
 
        SSttrriinngg FFoorrmmaattttiinngg
 
@@ -533,9 +537,9 @@
        Normally there are two space characters inserted between
        every two items printed into the graph. The space follow-
        ing a string can be suppressed by putting a \\gg at the end
-       of the string. The \\gg also squshes any space inside the
+       of the string. The \\gg also squashes any space inside the
        string if it is at the very end of the string. This can be
-       used in connection with %%ss to supress empty unit strings.
+       used in connection with %%ss to suppress empty unit strings.
 
         GPRINT:a:MAX:%lf%s\g
 
@@ -543,14 +547,14 @@
        vertical space before placing the next row of legends.
 
        When text has to be formated without special instructions
-       from your side, rrdtool will automatically justify the
+       from your side, RRDTool will automatically justify the
        text as soon as one string goes over the right edge. If
        you want to prevent the justification without forcing a
        newline, you can use the special tag \\JJ at the end of the
        string to disable the auto justification.
 
 NNOOTTEE oonn RReettuurrnn VVaalluueess
-       Whenever rrd_graph gets called, it prints a line telling
+       Whenever rrrrddggrraapphh gets called, it prints a line telling
        the size of the gif it has just created to STDOUT. This
        line looks like this: XSIZExYSIZE.
 
@@ -627,9 +631,9 @@
        hurting red to signal any unknown data.
 
        Note that this example assumes that your data is in the
-       positive half of the y-axis otherwhise you would would
-       have to add NEGINF in order to extend the coverage of the
-       rea to whole graph.
+       positive half of the y-axis otherwise you would have to
+       add NEGINF in order to extend the coverage of the rea to
+       whole graph.
 
 AAUUTTHHOORR
        Tobias Oetiker 
@@ -639,4 +643,4 @@
 
 
 
-1.0.45                      2003-02-19                RRDGRAPH(1)
+1.0.46                      2003-10-09                RRDGRAPH(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdinfo.html
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdinfo.html	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdinfo.html	Thu Jan 15 15:49:42 2004
@@ -25,7 +25,7 @@
 
 
 NAME
-rrdtool info - extract header information from an rrd
+rrdtool info - extract header information from an RRD
 PDF version.

 
 
@@ -35,7 +35,7 @@
 
 
 DESCRIPTION
-The info function prints the header information from an rrd in
+
The info function prints the header information from an RRD in
 a parsing friendly format.
 Check the rrdcreate manpage if you are uncertain about the meaning of the
 individual keys.
@@ -43,14 +43,14 @@
 
 
 EXAMPLE
-This is the output generated by running info on a simple rrd which
-contains two datasources and one rra. Note that the number after the
+
This is the output generated by running info on a simple RRD which
+contains two datasources and one RRA. Note that the number after the
 last_update keyword is in seconds since 1970. The string NaN
-stands for *UNKNOWN* data. In the example it means that this rrd
+stands for *UNKNOWN* data. In the example it means that this RRD
 has neither minimum not maximum values defined for either of its
 datasources.
 - filename = "randome.rrd"
+ filename = "random.rrd"
  rrd_version = "0001"
  step = 300
  last_update = 955892996

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdinfo.pod
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdinfo.pod	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdinfo.pod	Thu Jan 15 15:49:42 2004
@@ -1,6 +1,6 @@
 =head1 NAME
 
-rrdtool info - extract header information from an rrd
+rrdtool info - extract header information from an RRD
 
 =for html PDF version.
 
@@ -10,7 +10,7 @@
 
 =head1 DESCRIPTION
 
-The B function prints the header information from an rrd in
+The B function prints the header information from an RRD in
 a parsing friendly format.
 
 Check L if you are uncertain about the meaning of the
@@ -18,14 +18,14 @@
 
 =head1 EXAMPLE
 
-This is the output generated by running B on a simple rrd which
-contains two datasources and one rra. Note that the number after the
+This is the output generated by running B on a simple RRD which
+contains two datasources and one RRA. Note that the number after the
 I keyword is in seconds since 1970. The string B
-stands for I<*UNKNOWN*> data. In the example it means that this rrd
+stands for I<*UNKNOWN*> data. In the example it means that this RRD
 has neither minimum not maximum values defined for either of its
 datasources.
 
- filename = "randome.rrd"
+ filename = "random.rrd"
  rrd_version = "0001"
  step = 300
  last_update = 955892996

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdinfo.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdinfo.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdinfo.txt	Thu Jan 15 15:49:42 2004
@@ -3,27 +3,27 @@
 
 
 NNAAMMEE
-       rrdtool info - extract header information from an rrd
+       rrdtool info - extract header information from an RRD
 
 SSYYNNOOPPSSIISS
        rrrrddttooooll iinnffoo _f_i_l_e_n_a_m_e_._r_r_d
 
 DDEESSCCRRIIPPTTIIOONN
        The iinnffoo function prints the header information from an
-       rrd in a parsing friendly format.
+       RRD in a parsing friendly format.
 
        Check rrdcreate if you are uncertain about the meaning of
        the individual keys.
 
 EEXXAAMMPPLLEE
        This is the output generated by running iinnffoo on a simple
-       rrd which contains two datasources and one rra. Note that
+       RRD which contains two datasources and one RRA. Note that
        the number after the _l_a_s_t___u_p_d_a_t_e keyword is in seconds
        since 1970. The string NNaaNN stands for _*_U_N_K_N_O_W_N_* data. In
-       the example it means that this rrd has neither minimum not
+       the example it means that this RRD has neither minimum not
        maximum values defined for either of its datasources.
 
-        filename = "randome.rrd"
+        filename = "random.rrd"
         rrd_version = "0001"
         step = 300
         last_update = 955892996
@@ -56,4 +56,4 @@
 
 
 
-1.0.45                      2002-02-26                 RRDINFO(1)
+1.0.46                      2003-09-14                 RRDINFO(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdlast.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdlast.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdlast.txt	Thu Jan 15 15:49:42 2004
@@ -21,4 +21,4 @@
 
 
 
-1.0.45                      2002-02-26                 RRDLAST(1)
+1.0.46                      2002-02-26                 RRDLAST(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdresize.html
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdresize.html	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdresize.html	Thu Jan 15 15:49:42 2004
@@ -74,7 +74,7 @@
 
 
 NOTES
-The new .rrd file, with the modified RRAm, is written to the file 
+
The new .rrd file, with the modified RRAs, is written to the file 
 resize.rrd in the current directory.  The original .rrd file is not
 modified.
 It is possible to abuse this tool and get strange results

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdresize.pod
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdresize.pod	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdresize.pod	Thu Jan 15 15:49:42 2004
@@ -41,7 +41,7 @@
 
 =head1 NOTES
 
-The new .rrd file, with the modified RRAm, is written to the file 
+The new .rrd file, with the modified RRAs, is written to the file 
 B in the current directory.  The original .rrd file is not
 modified.
 

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdresize.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdresize.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdresize.txt	Thu Jan 15 15:49:42 2004
@@ -29,7 +29,7 @@
        _r_o_w_s    the number of rows you want to add or remove.
 
 NNOOTTEESS
-       The new .rrd file, with the modified RRAm, is written to
+       The new .rrd file, with the modified RRAs, is written to
        the file rreessiizzee..rrrrdd in the current directory.  The origi-
        nal .rrd file is not modified.
 
@@ -44,4 +44,4 @@
 
 
 
-1.0.45                      2002-07-05               RRDRESIZE(1)
+1.0.46                      2003-09-14               RRDRESIZE(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdrestore.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdrestore.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdrestore.txt	Thu Jan 15 15:49:42 2004
@@ -29,4 +29,4 @@
 
 
 
-1.0.45                      2002-02-26              RRDRESTORE(1)
+1.0.46                      2002-02-26              RRDRESTORE(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdtool.html
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdtool.html	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdtool.html	Thu Jan 15 15:49:42 2004
@@ -51,26 +51,26 @@
 things, ranging from the temperature in your office to the number of
 octets which have passed through the FDDI interface of your
 router. But it is not so trivial to store this data in a efficient and
-systematic manner. This is where rrdtool kicks in. It lets you
+systematic manner. This is where RRDTool kicks in. It lets you
 log and analyze the data you gather from all kinds of data-sources
-(DS). The data analysis part of rrdtool is based on the ability to
+(DS). The data analysis part of RRDTool is based on the ability to
 quickly generate graphical representations of the data values
 collected over a definable time period.
 In this man page you will find general information on the design and
-functionality of the Round Robin Database Tool (rrdtool). For a more
+functionality of the Round Robin Database Tool (RRDTool). For a more
 detailed description of how to use the individual functions of the
-rrdtool check the corresponding man page.
-For an introduction to the usage of rrdtool make sure you check the rrdtutorial manpage.
+RRDTool check the corresponding man page.
+For an introduction to the usage of RRDTool make sure you check the rrdtutorial manpage.
 
 
 FUNCTIONS
 While the man pages talk of command line switches you have to set in
-order to make rrdtool work it is important to note that the
-rrdtool can be 'remote controlled' through a set of pipes. This
+order to make RRDTool work it is important to note that the
+RRDTool can be 'remote controlled' through a set of pipes. This
 saves a considerable amount of startup time when you plan to make
-rrdtool do a lot of things quickly. Check the section on Remote Control further down. There is also a number of language bindings
-for rrdtool which allow you to use it directly from perl, python, tcl,
-php, ...
+RRDTool do a lot of things quickly. Check the section on Remote Control further down. There is also a number of language bindings
+for RRDTool which allow you to use it directly from Perl, Python, Tcl,
+Php, ...
 
 create

 
@@ -95,21 +95,21 @@
 
 
 Dump the contents of an RRD in plain ASCII. In connection with 
-restore you can use it to transport an rrd from one architecture to another.
+restore you can use it to transport an RRD from one architecture to another.
 Check the rrddump manpage.
 
 
 restore

 
 
-Restore an RRD in XML format to a binary rrd ... Check the rrdrestore manpage
+Restore an RRD in XML format to a binary RRD ... Check the rrdrestore manpage
 
 
 fetch

 
 
 Get data for a certain time period from a RRD. The graph function
-uses fetch to retrieve its data from an rrd. Check the rrdfetch manpage.
+uses fetch to retrieve its data from an RRD. Check the rrdfetch manpage.
 
 
 tune

@@ -145,7 +145,7 @@
 
rrdcgi

 
 
-This is a standalone tool for producing rrd graphs on the fly. Check
+This is a standalone tool for producing RRD graphs on the fly. Check
 the rrdcgi manpage.
 
 
@@ -159,7 +159,7 @@
 When monitoring the state of a system, it is convenient to have the
 data available at a constant interval. Unfortunately you may not
 always be able to fetch data at exactly the time you want
-to. Therefore rrdtool lets you update the logfile at any time you
+to. Therefore RRDTool lets you update the logfile at any time you
 want. It will automatically interpolate the value of the data-source
 (DS) at the latest official time-slot and write this value to the
 log. The value you have supplied is stored as well and is also taken
@@ -174,12 +174,12 @@
 could do this by simply storing the data in 1 minute interval, for one
 year. While this would take considerable disk space it would also take
 a lot of time to analyze the data when you wanted to create a graph
-covering the whole year. rrdtool offers a solution to this
+covering the whole year. RRDTool offers a solution to this
 problem through its data consolidation feature. When setting up
 an Round Robin Database (RRD), you can define at which interval
 this consolidation should occur, and what consolidation function
 (CF) (average, minimum, maximum, last) should be used to
-build the consolidated values (see rrdcreate). You can define any
+build the consolidated values (see the rrdcreate manpage). You can define any
 number of different consolidation setups within one RRD. They will
 all be maintained on the fly when new data is loaded into the RRD.
 
@@ -194,7 +194,7 @@
 
 
 It works like this: If you want to store 1000 values in 5 minute
-interval, rrdtool will allocate space for 1000 data values and a
+interval, RRDTool will allocate space for 1000 data values and a
 header area. In the header it will store a pointer telling
 which one of the values in the storage area was last written to. New
 values are written to the Round Robin Archive in a ...  you guess it
@@ -221,7 +221,7 @@
 As mentioned earlier, the RRD stores data at a constant
 interval. Now it may happen that no new data is available when a
 value has to be written to the RRD. Data acquisition may not be
-possible for one reason or an other. The rrdtool handles these
+possible for one reason or an other. The RRDTool handles these
 situations by storing an *UNKNOWN* value into the database. The
 value '*UNKNOWN*' is supported through all the functions of the
 database. When consolidating the amount of *UNKNOWN* data is
@@ -235,7 +235,7 @@
 
Graphing

 
 
-The rrdtool also allows one to generate reports in numerical and
+The RRDTool also allows one to generate reports in numerical and
 graphical form based on the data stored in one or several
 RRDs. The graphing feature is fully configurable. Size, color and
 contents of the graph can be defined freely. Check the rrdgraph manpage
@@ -245,15 +245,15 @@
 
 
 REMOTE CONTROL
-When you start rrdtool with the command line option '-', it waits
+
When you start RRDTool with the command line option '-', it waits
 for input via standard in. With this feature you can improve
-performance by attaching rrdtool to another process (mrtg is one
-example) through a set of pipes. Over the pipes rrdtool accepts the
+performance by attaching RRDTool to another process (MRTG is one
+example) through a set of pipes. Over the pipes RRDTool accepts the
 same arguments as on the command line. When a command is completed, 
-rrdtool will print the string  'OK', followed by timing information of
+RRDTool will print the string  'OK', followed by timing information of
 the form u:usertime s:systemtime both values are running
-totals of seconds since rrdtool was started. If an error occurs, a line 
-of the form 'ERROR: Description of error' will be printed. rrdtool
+totals of seconds since RRDTool was started. If an error occurs, a line 
+of the form 'ERROR: Description of error' will be printed. RRDTool
 will not abort if possible, but follow the ERROR line with an OK line.
 
 

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdtool.pod
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdtool.pod	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdtool.pod	Thu Jan 15 15:49:42 2004
@@ -16,29 +16,29 @@
 things, ranging from the temperature in your office to the number of
 octets which have passed through the FDDI interface of your
 router. But it is not so trivial to store this data in a efficient and
-systematic manner. This is where B kicks in. It lets you
+systematic manner. This is where B kicks in. It lets you
 I the data you gather from all kinds of data-sources
-(B). The data analysis part of rrdtool is based on the ability to
+(B). The data analysis part of RRDTool is based on the ability to
 quickly generate graphical representations of the data values
 collected over a definable time period.
 
 In this man page you will find general information on the design and
-functionality of the Round Robin Database Tool (rrdtool). For a more
+functionality of the Round Robin Database Tool (RRDTool). For a more
 detailed description of how to use the individual functions of the
-B check the corresponding man page.
+B check the corresponding man page.
 
-For an introduction to the usage of rrdtool make sure you check L.
+For an introduction to the usage of RRDTool make sure you check L.
 
 =head2 FUNCTIONS
 
 While the man pages talk of command line switches you have to set in
-order to make B work it is important to note that the
-B can be 'remote controlled' through a set of pipes. This
+order to make B work it is important to note that the
+B can be 'remote controlled' through a set of pipes. This
 saves a considerable amount of startup time when you plan to make
-B do a lot of things quickly. Check the section on L<"Remote
+B do a lot of things quickly. Check the section on L<"Remote
 Control"> further down. There is also a number of language bindings
-for rrdtool which allow you to use it directly from perl, python, tcl,
-php, ...
+for RRDTool which allow you to use it directly from Perl, Python, Tcl,
+Php, ...
 
 =over 8
 
@@ -58,17 +58,17 @@
 =item B
 
 Dump the contents of an RRD in plain ASCII. In connection with 
-restore you can use it to transport an rrd from one architecture to another.
+restore you can use it to transport an RRD from one architecture to another.
 Check L.
 
 =item B
 
-Restore an RRD in XML format to a binary rrd ... Check L
+Restore an RRD in XML format to a binary RRD ... Check L
 
 =item B
 
 Get data for a certain time period from a RRD. The graph function
-uses fetch to retrieve its data from an rrd. Check L.
+uses fetch to retrieve its data from an RRD. Check L.
 
 =item B
 
@@ -92,7 +92,7 @@
 
 =item B
 
-This is a standalone tool for producing rrd graphs on the fly. Check
+This is a standalone tool for producing RRD graphs on the fly. Check
 L.
 
 =back
@@ -106,7 +106,7 @@
 When monitoring the state of a system, it is convenient to have the
 data available at a constant interval. Unfortunately you may not
 always be able to fetch data at exactly the time you want
-to. Therefore B lets you update the logfile at any time you
+to. Therefore B lets you update the logfile at any time you
 want. It will automatically interpolate the value of the data-source
 (B) at the latest official time-slot and write this value to the
 log. The value you have supplied is stored as well and is also taken
@@ -119,12 +119,12 @@
 could do this by simply storing the data in 1 minute interval, for one
 year. While this would take considerable disk space it would also take
 a lot of time to analyze the data when you wanted to create a graph
-covering the whole year. B offers a solution to this
+covering the whole year. B offers a solution to this
 problem through its data consolidation feature. When setting up
 an Round Robin Database (B), you can define at which interval
 this consolidation should occur, and what consolidation function
 (B) (average, minimum, maximum, last) should be used to
-build the consolidated values (see rrdcreate). You can define any
+build the consolidated values (see L). You can define any
 number of different consolidation setups within one B. They will
 all be maintained on the fly when new data is loaded into the B.
 
@@ -136,7 +136,7 @@
 space. 
 
 It works like this: If you want to store 1000 values in 5 minute
-interval, B will allocate space for 1000 data values and a
+interval, B will allocate space for 1000 data values and a
 header area. In the header it will store a pointer telling
 which one of the values in the storage area was last written to. New
 values are written to the Round Robin Archive in a ...  you guess it
@@ -160,7 +160,7 @@
 As mentioned earlier, the B stores data at a constant
 interval. Now it may happen that no new data is available when a
 value has to be written to the B. Data acquisition may not be
-possible for one reason or an other. The B handles these
+possible for one reason or an other. The B handles these
 situations by storing an I<*UNKNOWN*> value into the database. The
 value 'I<*UNKNOWN*>' is supported through all the functions of the
 database. When consolidating the amount of I<*UNKNOWN*> data is
@@ -172,7 +172,7 @@
 
 =item Graphing
 
-The B also allows one to generate reports in numerical and
+The B also allows one to generate reports in numerical and
 graphical form based on the data stored in one or several
 Bs. The graphing feature is fully configurable. Size, color and
 contents of the graph can be defined freely. Check L
@@ -182,15 +182,15 @@
 
 =head2 REMOTE CONTROL
 
-When you start B with the command line option 'B<->', it waits
+When you start B with the command line option 'B<->', it waits
 for input via standard in. With this feature you can improve
-performance by attaching B to another process (mrtg is one
-example) through a set of pipes. Over the pipes B accepts the
+performance by attaching B to another process (MRTG is one
+example) through a set of pipes. Over the pipes B accepts the
 same arguments as on the command line. When a command is completed, 
-rrdtool will print the string  'C', followed by timing information of
+RRDTool will print the string  'C', followed by timing information of
 the form BI BI both values are running
-totals of seconds since rrdtool was started. If an error occurs, a line 
-of the form 'C I' will be printed. B
+totals of seconds since RRDTool was started. If an error occurs, a line 
+of the form 'C I' will be printed. B
 will not abort if possible, but follow the ERROR line with an OK line.
 
 

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdtool.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdtool.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdtool.txt	Thu Jan 15 15:49:42 2004
@@ -16,32 +16,32 @@
        office to the number of octets which have passed through
        the FDDI interface of your router. But it is not so triv-
        ial to store this data in a efficient and systematic man-
-       ner. This is where rrrrddttooooll kicks in. It lets you _l_o_g _a_n_d
+       ner. This is where RRRRDDTTooooll kicks in. It lets you _l_o_g _a_n_d
        _a_n_a_l_y_z_e the data you gather from all kinds of data-sources
-       (DDSS). The data analysis part of rrdtool is based on the
+       (DDSS). The data analysis part of RRDTool is based on the
        ability to quickly generate graphical representations of
        the data values collected over a definable time period.
 
        In this man page you will find general information on the
        design and functionality of the Round Robin Database Tool
-       (rrdtool). For a more detailed description of how to use
-       the individual functions of the rrrrddttooooll check the corre-
+       (RRDTool). For a more detailed description of how to use
+       the individual functions of the RRRRDDTTooooll check the corre-
        sponding man page.
 
-       For an introduction to the usage of rrdtool make sure you
+       For an introduction to the usage of RRDTool make sure you
        check rrdtutorial.
 
        FFUUNNCCTTIIOONNSS
 
        While the man pages talk of command line switches you have
-       to set in order to make rrrrddttooooll work it is important to
-       note that the rrrrddttooooll can be 'remote controlled' through a
+       to set in order to make RRRRDDTTooooll work it is important to
+       note that the RRRRDDTTooooll can be 'remote controlled' through a
        set of pipes. This saves a considerable amount of startup
-       time when you plan to make rrrrddttooooll do a lot of things
+       time when you plan to make RRRRDDTTooooll do a lot of things
        quickly. Check the section on "Remote Control" further
-       down. There is also a number of language bindings for rrd-
-       tool which allow you to use it directly from perl, python,
-       tcl, php, ...
+       down. There is also a number of language bindings for RRD-
+       Tool which allow you to use it directly from Perl, Python,
+       Tcl, Php, ...
 
        ccrreeaattee  Set up a new Round Robin Database (RRD). Check
                rrdcreate.
@@ -55,15 +55,15 @@
 
        dduummpp    Dump the contents of an RRD in plain ASCII. In
                connection with restore you can use it to trans-
-               port an rrd from one architecture to another.
+               port an RRD from one architecture to another.
                Check rrddump.
 
-       rreessttoorree Restore an RRD in XML format to a binary rrd ...
+       rreessttoorree Restore an RRD in XML format to a binary RRD ...
                Check rrdrestore
 
        ffeettcchh   Get data for a certain time period from a RRD. The
                graph function uses fetch to retrieve its data
-               from an rrd. Check rrdfetch.
+               from an RRD. Check rrdfetch.
 
        ttuunnee    Alter setup of an RRD. Check rrdtune.
 
@@ -78,7 +78,7 @@
        xxppoorrtt   Export data retrieved from one or several RRD.
                Check rrdxport
 
-       rrrrddccggii  This is a standalone tool for producing rrd graphs
+       rrrrddccggii  This is a standalone tool for producing RRD graphs
                on the fly. Check rrdcgi.
 
        HHOOWW DDOOEESS RRRRDDTTOOOOLL WWOORRKK??
@@ -89,7 +89,7 @@
                venient to have the data available at a constant
                interval. Unfortunately you may not always be able
                to fetch data at exactly the time you want to.
-               Therefore rrrrddttooooll lets you update the logfile at
+               Therefore RRRRDDTTooooll lets you update the logfile at
                any time you want. It will automatically interpo-
                late the value of the data-source (DDSS) at the lat-
                est official time-slot and write this value to the
@@ -105,7 +105,7 @@
                one year. While this would take considerable disk
                space it would also take a lot of time to analyze
                the data when you wanted to create a graph cover-
-               ing the whole year. rrrrddttooooll offers a solution to
+               ing the whole year. RRRRDDTTooooll offers a solution to
                this problem through its data consolidation fea-
                ture. When setting up an Round Robin Database
                (RRRRDD), you can define at which interval this con-
@@ -125,7 +125,7 @@
                storage space.
 
                It works like this: If you want to store 1000 val-
-               ues in 5 minute interval, rrrrddttooooll will allocate
+               ues in 5 minute interval, RRRRDDTTooooll will allocate
                space for 1000 data values and a header area. In
                the header it will store a pointer telling which
                one of the values in the storage area was last
@@ -155,7 +155,7 @@
                constant interval. Now it may happen that no new
                data is available when a value has to be written
                to the RRRRDD. Data acquisition may not be possible
-               for one reason or an other. The rrrrddttooooll handles
+               for one reason or an other. The RRRRDDTTooooll handles
                these situations by storing an _*_U_N_K_N_O_W_N_* value
                into the database. The value '_*_U_N_K_N_O_W_N_*' is sup-
                ported through all the functions of the database.
@@ -168,7 +168,7 @@
                _*_U_N_K_N_O_W_N_* value will be written to the RRRRAA.
 
        Graphing
-               The rrrrddttooooll also allows one to generate reports in
+               The RRRRDDTTooooll also allows one to generate reports in
                numerical and graphical form based on the data
                stored in one or several RRRRDDs. The graphing fea-
                ture is fully configurable. Size, color and con-
@@ -177,17 +177,17 @@
 
        RREEMMOOTTEE CCOONNTTRROOLL
 
-       When you start rrrrddttooooll with the command line option '--',
+       When you start RRRRDDTTooooll with the command line option '--',
        it waits for input via standard in. With this feature you
-       can improve performance by attaching rrrrddttooooll to another
-       process (mrtg is one example) through a set of pipes. Over
-       the pipes rrrrddttooooll accepts the same arguments as on the
-       command line. When a command is completed, rrdtool will
+       can improve performance by attaching RRRRDDTTooooll to another
+       process (MRTG is one example) through a set of pipes. Over
+       the pipes RRRRDDTTooooll accepts the same arguments as on the
+       command line. When a command is completed, RRDTool will
        print the string  '"OK"', followed by timing information
        of the form uu::_u_s_e_r_t_i_m_e ss::_s_y_s_t_e_m_t_i_m_e both values are run-
-       ning totals of seconds since rrdtool was started. If an
+       ning totals of seconds since RRDTool was started. If an
        error occurs, a line of the form '"ERROR:" _D_e_s_c_r_i_p_t_i_o_n _o_f
-       _e_r_r_o_r' will be printed. rrrrddttooooll will not abort if possi-
+       _e_r_r_o_r' will be printed. RRRRDDTTooooll will not abort if possi-
        ble, but follow the ERROR line with an OK line.
 
 SSEEEE AALLSSOO
@@ -202,4 +202,4 @@
 
 
 
-1.0.45                      2002-11-29                 RRDTOOL(1)
+1.0.46                      2003-09-14                 RRDTOOL(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdtune.html
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdtune.html	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdtune.html	Thu Jan 15 15:49:42 2004
@@ -60,7 +60,7 @@
 
 

 modify the heartbeat of a data source. By setting this to a high
-value the rrd will accept things like one value per day ...
+value the RRD will accept things like one value per day ...
 
 
 --minimum|-i ds-name:min

@@ -96,8 +96,8 @@
 rrdtool tune data.rrd -h in:100000 -h out:100000 -h through:100000
 Set the minimum required heartbeat for data sources 'in', 'out' 
 and 'through' to 10000 seconds which is a little over one day in data.rrd.
-This would allow to feed old data from mrtg-2.0 right into
-rrdtool without generating *UNKNOWN* entries.
+This would allow to feed old data from MRTG-2.0 right into
+RRDTool without generating *UNKNOWN* entries.
 
 
 

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdtune.pod
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdtune.pod	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdtune.pod	Thu Jan 15 15:49:42 2004
@@ -35,7 +35,7 @@
 =item S|B<-h> I:I>
 
 modify the I of a data source. By setting this to a high
-value the rrd will accept things like one value per day ...
+value the RRD will accept things like one value per day ...
 
 =item S|B<-i> I:I>
 
@@ -63,8 +63,8 @@
 
 Set the minimum required heartbeat for data sources 'in', 'out' 
 and 'through' to 10000 seconds which is a little over one day in data.rrd.
-This would allow to feed old data from mrtg-2.0 right into
-rrdtool without generating *UNKNOWN* entries.
+This would allow to feed old data from MRTG-2.0 right into
+RRDTool without generating *UNKNOWN* entries.
 
 =head1 AUTHOR
 

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdtune.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdtune.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdtune.txt	Thu Jan 15 15:49:42 2004
@@ -30,7 +30,7 @@
 
        ----hheeaarrttbbeeaatt|--hh _d_s_-_n_a_m_e:_h_e_a_r_t_b_e_a_t
                modify the _h_e_a_r_t_b_e_a_t of a data source. By setting
-               this to a high value the rrd will accept things
+               this to a high value the RRD will accept things
                like one value per day ...
 
        ----mmiinniimmuumm|--ii _d_s_-_n_a_m_e:_m_i_n
@@ -56,7 +56,7 @@
        Set the minimum required heartbeat for data sources 'in',
        'out' and 'through' to 10000 seconds which is a little
        over one day in data.rrd.  This would allow to feed old
-       data from mrtg-2.0 right into rrdtool without generating
+       data from MRTG-2.0 right into RRDTool without generating
        *UNKNOWN* entries.
 
 AAUUTTHHOORR
@@ -64,4 +64,4 @@
 
 
 
-1.0.45                      2002-02-26                 RRDTUNE(1)
+1.0.46                      2003-09-14                 RRDTUNE(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdtutorial.es.txt
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdtutorial.es.txt	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdtutorial.es.txt	Thu Jan 15 15:49:42 2004
@@ -1262,4 +1262,4 @@
 
 
 
-1.0.45                      2003-01-20          RRDTUTORIAL.ES(1)
+1.0.46                      2003-01-20          RRDTUTORIAL.ES(1)

Modified: trunk/orca/packages/rrdtool-1.0.46/doc/rrdtutorial.html
==============================================================================
--- trunk/orca/packages/rrdtool-1.0.45-to-1.0.46-upgrade/doc/rrdtutorial.html	(original)
+++ trunk/orca/packages/rrdtool-1.0.46/doc/rrdtutorial.html	Thu Jan 15 15:49:42 2004
@@ -19,8 +19,8 @@
 	
 
 		Important
-		What is RRDtool ?
-		What data can be put into an RDD ?
+		What is RRDTool ?
+		What data can be put into an RRD ?
 		What can I do with this tool ?
 		What if I still have problems after reading this document ?
 		How will you help me ?
@@ -35,7 +35,7 @@
 		Consolidation Functions
 		Let's review what you now should know.
 		Data Source Types
-		RRDtool under the Microscope
+		RRDTool under the Microscope
 		Counter Wraps
 		Data Resampling
 	
@@ -51,18 +51,18 @@
 
 
 NAME
-rrdtutorial - Alex van den Bogaerdt's RRDtool tutorial
+rrdtutorial - Alex van den Bogaerdt's RRDTool tutorial
 Go Spanish
PDF version.

 
 
 DESCRIPTION
-RRDtool is written by Tobias Oetiker <oetiker at ee.ethz.ch> with
+
RRDTool is written by Tobias Oetiker <oetiker at ee.ethz.ch> with
 contributions from many people all around the world. This document is
 written by Alex van den Bogaerdt <alex at ergens.op.het.net> to help you
-understand what RRDtool is and what it can do for you.
-The documentation provided with RRDtool can be too technical for some
+understand what RRDTool is and what it can do for you.
+The documentation provided with RRDTool can be too technical for some
 people. This tutorial is here to help you understand the basics of
-RRDtool. It should prepare you to read the documentation yourself.
+RRDTool. It should prepare you to read the documentation yourself.
 It also explains the general things about statistics with a focus on
 networking.
 
@@ -77,8 +77,8 @@
 understand the basics, the examples will not be as meaningful to you.
 
 
-What is RRDtool ?
-RRDtool refers to Round Robin Database tool.
+
What is RRDTool ?
+RRDTool refers to Round Robin Database tool.
 Round robin is a technique that works with a fixed amount of data, and a
 pointer to the current element. Think of a circle with some dots plotted
 on the edge, these dots are the places where data can be stored. Draw an
@@ -87,15 +87,15 @@
 element. As we are on a circle there is no beginning nor an end, you can
 go on and on. After a while, all the available places will be used and
 the process automatically reuses old locations. This way, the database
-will not grow in size and therefore requires no mainenance.
-RRDtool works with with Round Robin Databases (RRDs). It stores and retrieves
+will not grow in size and therefore requires no maintenance.
+RRDTool works with with Round Robin Databases (RRDs). It stores and retrieves
 data from them.
 
 
-What data can be put into an RDD ?
+What data can be put into an RRD ?
 You name it, it will probably fit. You should be able to measure some value
-at several points in time and provide this information to RRDtool. If you
-can do this, RRDtool will be able to store it. The values need to be
+at several points in time and provide this information to RRDTool. If you
+can do this, RRDTool will be able to store it. The values need to be
 numerical but don't have to be, as opposed to MRTG, integers.
 Many examples talk about SNMP which is an acronym for
 Simple Network Management Protocol. ``Simple'' refers to the protocol --
@@ -107,14 +107,14 @@
 

 
 What can I do with this tool ?
-RRDtool originated from MRTG (Multi Router Traffic Grapher).  MRTG started
+
RRDTool originated from MRTG (Multi Router Traffic Grapher).  MRTG started
 as a tiny little script for graphing the use of a connection
 to the Internet. MRTG evolved into a tool for graphing other data sources
 including temperature, speed, voltage, number of printouts and
-the like. Most likely you will start to use the RRDtool to store
+the like. Most likely you will start to use the RRDTool to store
 and process data collected via SNMP. The data will most likely be bytes
 (or bits) transfered from and to a network or a computer.
-RRDtool lets you create a database, store data in it, retrieve that data
+RRDTool lets you create a database, store data in it, retrieve that data
 and create graphs in GIF format for display on a web browser. Those GIF
 images are dependent on the data you collected and could be, for instance,
 an overview of the average network usage, or the peaks that occurred.
@@ -122,13 +122,13 @@
 consumption, number of visitors at an exhibition, noise levels near an
 airport, temperature on your favorite holiday location, temperature in the
 fridge and whatever you imagination can come up with. You need a sensor to
-measure the data and be able to feed the numbers to RRDtool.
+measure the data and be able to feed the numbers to RRDTool.
 
 
 What if I still have problems after reading this document ?
 First of all: read it again! You may have missed something.
 If you are unable to compile the sources and you have a fairly common
-OS, it will probably not be the fault of RRDtool. There may be precompiled
+OS, it will probably not be the fault of RRDTool. There may be precompiled
 versions around on the Internet. If they come from trusted sources, get
 one of those.
 If on the other hand the program works but does not give you the
@@ -139,7 +139,7 @@
 a question without searching the archives: your problem may already have been
 solved for somebody else!  This is true for most, if not all, mailing lists
 and not only for this particular list! Look in the documentation that
-came with RRDtool for the location and usage of the list.
+came with RRDTool for the location and usage of the list.
 I suggest you take a moment to subscribe to the mailing list right now
 by sending an email to <rrd-users-request at list.ee.ethz.ch> with a
 subject of ``subscribe''. If you ever want to leave this list, you write
@@ -149,7 +149,7 @@
 
How will you help me ?
 By giving you some detailed descriptions with detailed examples.
 It is assumed that following the instructions in the order presented
-will give you enough knowledge of RRDtool to experiment for yourself.
+will give you enough knowledge of RRDTool to experiment for yourself.
 If it doesn't work the first time, don't give up. Reread the stuff that
 you did understand, you may have missed something.
 By following the examples you get some hands-on experience and, even
@@ -248,11 +248,11 @@
 this document. It holds one data source (DS) named ``speed'' that gets
 built from a counter. This counter is read every five minutes (default)
 In the same database two round robin archives (RRAs) are kept, one
-averages the data every time it is read (eg there's nothing to average)
+averages the data every time it is read (e.g. there's nothing to average)
 and keeps 24 samples (24 times 5 minutes is 2 hours). The other averages
-6 values (half hour) and contains 10 of such averages (eg 5 hours)
+6 values (half hour) and contains 10 of such averages (e.g. 5 hours)
 The remaining options will be discussed later on.
-RRDtool works with special time stamps coming from the UNIX world.
+
RRDTool works with special time stamps coming from the UNIX world.
 This time stamp is the number of seconds that passed since January
 1st 1970 UTC.  This time stamp is translated into local time and
 it will therefore look different for the different time zones.
@@ -365,8 +365,8 @@
 The vertical axis displays the range we entered. We provided kilometers
 and when divided by 300 seconds, we get very small numbers. To be exact,
 the first value was 12 (12357-12345) and divided by 300 this makes 0.04,
-which is displayed by RRDtool as ``40 m'' meaning ``40/1000''. The ``m'' has
-nothing to do with meters, kilometers or millimeters! RRDtool doesn't
+which is displayed by RRDTool as ``40 m'' meaning ``40/1000''. The ``m'' has
+nothing to do with meters, kilometers or millimeters! RRDTool doesn't
 know about all this, it just works with numbers and not with meters...
 What we did wrong was that we should have measured in meters, this would
 have been (12357000-12345000)/300 = 12000/300 = 40.
@@ -423,7 +423,7 @@
 
 
 Graphics Magic
-I like to believe there are virtually no limits to how RRDtool graph
+
I like to believe there are virtually no limits to how RRDTool graph
 can manipulate data. I will not explain how it works, but look at the
 following GIF:
 @@ -460,7 +460,7 @@
 We've already used the ``update'' command: it took one or more parameters
 in the form of ``<time>:<value>''. You'll be glad to know that you can
 get the current time by filling in a ``N'' as the time.
-If you wish, you can also use the ``time'' function in perl.
+If you wish, you can also use the ``time'' function in Perl.
 The shortest example in this doc :)
     perl -e 'print time, "\n" '
@@ -522,7 +522,7 @@
 worse, they have several default prefixes ...
 Right, lets continue to the start of our OID: we had 1.3.6.1.2.1
 From there, we are especially interested in the branch ``interfaces''
-which has number 2 (eg 1.3.6.1.2.1.2 or 1.3.6.1.2.1.interfaces).
+which has number 2 (e.g. 1.3.6.1.2.1.2 or 1.3.6.1.2.1.interfaces).
 First, we have to get some SNMP program. First look if there is a
 pre-compiled package available for your OS. This is the preferred way.
 If not, you will have to get yourself the sources and compile those.
@@ -601,7 +601,7 @@
  600 2-hour samples:     50   days
  732 1-day samples:     732   days
 These ranges are appended so the total amount of data kept is approximately
-797 days.  RRDtool stores the data differently, it doesn't start the ``weekly''
+797 days.  RRDTool stores the data differently, it doesn't start the ``weekly''
 archive where the ``daily'' archive stopped.  For both archives the most recent
 data will be near ``now'' and therefore we will need to keep more data than
 MRTG does!
@@ -703,7 +703,7 @@
 get a totally different picture. You would see the same values on the
 average and maximum graphs (provided I measured every 300 seconds).
 You would be able to see when I stopped, when I was in top gear, when
-I drove over fast hiways etc. The granularity of the data is much
+I drove over fast highways etc. The granularity of the data is much
 higher, so you can see more. However, this takes 12 samples per hour,
 or 288 values per day, so it would be too much to keep for a long
 period of time. Therefore we average it, eventually to one value per
@@ -722,7 +722,7 @@
 database and view the outcome instead of the raw data.
 You know about the difference between averages and maxima, and when
 to use which (or at least you have an idea).
-RRDtool can do more than what we have learned up to now. Before you
+
RRDTool can do more than what we have learned up to now. Before you
 continue with the rest of this doc, I recommend that you reread from
 the start and try some modifications on the examples. Make sure you
 fully understand everything. It will be worth the effort and helps
@@ -741,8 +741,8 @@
 so called hot-spot and the exhaust.  These values are not counters.
 If I take the difference of the two samples and divide that by
 300 seconds I would be asking for the temperature change per second.
-Hopefully this is zero! If not, the computerroom is on fire :)
-So, what can we do ?  We can tell RRDtool to store the values we measure
+Hopefully this is zero! If not, the computer room is on fire :)
+So, what can we do ?  We can tell RRDTool to store the values we measure
 directly as they are (this is not entirely true but close enough). The
 graphs we make will look much better, they will show a rather constant
 value. I know when the router is busy (it
@@ -759,9 +759,9 @@
  - DERIVE
  - ABSOLUTE
 The two new types are DERIVE and ABSOLUTE. Absolute can be used like
-counter with one difference: RRDtool assumes the counter is reset when
-it's read. That is: its delta is known without calculation by RRDtool
-whereas RRDtool needs to calculate it for the counter type.
+counter with one difference: RRDTool assumes the counter is reset when
+it's read. That is: its delta is known without calculation by RRDTool
+whereas RRDTool needs to calculate it for the counter type.
 Example: our first example (12345, 12357, 12363, 12363) would read:
 unknown, 12, 6, 0. The rest of the calculations stay the same.
 The other one, derive, is like counter. Unlike counter, it can also
@@ -793,11 +793,11 @@
             DEF:lined=all.rrd:d:AVERAGE LINE3:lined#000000:"Line D"