diff --git a/doc/rrdtool.pod b/doc/rrdtool.pod
index 73fc34a7ed91b7adee20c2b74c724e30b3c55043..0d701ca4a420818fd431cb47c57d1b40e222ea9a 100644 (file)
--- a/doc/rrdtool.pod
+++ b/doc/rrdtool.pod
Export data retrieved from one or several RRDs. Check L<rrdxport>.
-=item B<flush>
+=item B<flushcached>
-Flush the values for a specific RRD file from memory. Check L<rrdflush>.
+Flush the values for a specific RRD file from memory. Check L<rrdflushcached>.
=item B<rrdcgi>
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 B<RRDtool> lets you update the logfile at any time you
+to. Therefore B<RRDtool> lets you update the log file at any time you
want. It will automatically interpolate the value of the data-source
(B<DS>) at the latest official time-slot (interval) and write this
interpolated value to the log. The original value you have supplied is
For very big setups, updating thousands of RRD files often becomes a serious IO
problem. If you run into such problems, you might want to take a look at
-L<rrdcached>, a caching daemon for RRDTool which may help you lessen the
+L<rrdcached>, a caching daemon for RRDtool which may help you lessen the
stress on your disks.
=head1 SEE ALSO
rrdcreate, rrdupdate, rrdgraph, rrddump, rrdfetch, rrdtune, rrdlast, rrdxport,
-rrdflush, rrdcached
+rrdflushcached, rrdcached
=head1 BUGS