summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: a41958e)
raw | patch | inline | side by side (parent: a41958e)
author | oetiker <oetiker@a5681a0c-68f1-0310-ab6d-d61299d08faa> | |
Sun, 21 May 2006 21:53:57 +0000 (21:53 +0000) | ||
committer | oetiker <oetiker@a5681a0c-68f1-0310-ab6d-d61299d08faa> | |
Sun, 21 May 2006 21:53:57 +0000 (21:53 +0000) |
git-svn-id: svn://svn.oetiker.ch/rrdtool/branches/1.2/program@833 a5681a0c-68f1-0310-ab6d-d61299d08faa
doc/rrd-beginners.pod | patch | blob | history |
diff --git a/doc/rrd-beginners.pod b/doc/rrd-beginners.pod
index c3d0a397155a5dd7a698f81377d7fcc8bc7bb8c0..f96b93bcc850399b8e50a381fc7c88a93109e48c 100644 (file)
--- a/doc/rrd-beginners.pod
+++ b/doc/rrd-beginners.pod
other number which might also be a valid data value. For example, the
traffic flow counter on a router keeps increasing. Lets say, a value
is missed for an interval and 0 is stored instead of UNKNOWN. Now when
-hte next value becomes available, it will calculate the difference
+the next value becomes available, it will calculate the difference
between the current value and the previous value (0) which is not
correct. So, inserting the value UNKNOWN makes much more sense here.