diff --git a/doc/rrdtool.1 b/doc/rrdtool.1
index 3fe94f609035d1b653a79ebdd07cc0f5b9debb20..155508f17db2481e6ed953eb71e0c4b261000d1b 100644 (file)
--- a/doc/rrdtool.1
+++ b/doc/rrdtool.1
-.\" Automatically generated by Pod::Man 2.1801 (Pod::Simple 3.08)
+.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "RRDTOOL 1"
-.TH RRDTOOL 1 "2009-06-09" "1.3.999" "rrdtool"
+.TH RRDTOOL 1 "2013-05-23" "1.4.8" "rrdtool"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
When monitoring the state of a system, it is convenient to have the
data available at a constant time interval. Unfortunately, you may not
always be able to fetch data at exactly the time you want
-to. Therefore \fBRRDtool\fR lets you update the logfile at any time you
+to. Therefore \fBRRDtool\fR lets you update the log file at any time you
want. It will automatically interpolate the value of the data-source
(\fB\s-1DS\s0\fR) at the latest official time-slot (interval) and write this
interpolated value to the log. The original value you have supplied is
.IX Header "RRDCACHED, THE CACHING DAEMON"
For very big setups, updating thousands of \s-1RRD\s0 files often becomes a serious \s-1IO\s0
problem. If you run into such problems, you might want to take a look at
-rrdcached, a caching daemon for RRDTool which may help you lessen the
+rrdcached, a caching daemon for RRDtool which may help you lessen the
stress on your disks.
.SH "SEE ALSO"
.IX Header "SEE ALSO"