X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=doc%2Frrdgraph_libdbi.pod;h=1e4aa4db1848bf58efe18abc2d73d443f803f318;hb=d85e6bdfe82fdc4d16898df43f8a5371503816ae;hp=a6b48cc60916252b6d28b954b6982c920ea5328d;hpb=b69a1a9abc9afdc2bfb23b84e28c2afb0b1a5e09;p=rrdtool.git

diff --git a/doc/rrdgraph_libdbi.pod b/doc/rrdgraph_libdbi.pod
index a6b48cc..1e4aa4d 100644
--- a/doc/rrdgraph_libdbi.pod
+++ b/doc/rrdgraph_libdbi.pod
@@ -4,7 +4,7 @@ rrdgraph_libdbi - fetching data for graphing in rrdtool graph via libdbi
 
 =head1 SYNOPSIS
 
-E<lt>rrdfileE<gt> = B<sql//E<lt>libdbi driverE<gt>/E<lt>driver-option-nameE<gt>=E<lt>driver-option-valueE<gt>/...[/rrdminstepsize=E<lt>stepsizeE<gt>][/rrdfillmissing=E<lt>fill missing n samplesE<gt>]//E<lt>tableE<gt>/E<lt>unixtimestamp columnE<gt>/E<lt>data value columnE<gt>[/derive]/E<lt>where clause 1E<gt>/.../E<lt>where clause nE<gt>>
+E<lt>rrdfileE<gt> = B<sql//E<lt>libdbi driverE<gt>/E<lt>driver-option-nameE<gt>=E<lt>driver-option-valueE<gt>/...[/rrdminstepsize=E<lt>stepsizeE<gt>][/rrdfillmissing=E<lt>fill missing n secondsE<gt>]//E<lt>tableE<gt>/E<lt>unixtimestamp columnE<gt>/E<lt>data value columnE<gt>[/derive]/E<lt>where clause 1E<gt>/.../E<lt>where clause nE<gt>>
 
 =head1 DESCRIPTION
 
@@ -29,9 +29,9 @@ This pseudo-rrd-filename defines a sql datasource:
 
   defines the minimum number of the step-length used for graphing (default: 300 seconds)
 
-=item B</rrdfillmissing>=B<E<lt>fill missing stepsE<gt>>
+=item B</rrdfillmissing>=B<E<lt>fill missing secondsE<gt>>
 
-  defines the number of steps to fill with the last value to avoid NaN boxes due to data-insertation jitter (default: 0 steps)
+  defines the number of seconds to fill with the last value to avoid NaN boxes due to data-insertation jitter (default: 0 seconds)
 
 =item B<E<lt>tableE<gt>>
 
@@ -121,11 +121,11 @@ To illustrate this here a command to create a graph that contains the actual val
 
 * Naturally you can also use any other kind of driver that libdbi supports - e.g postgres, ...
 
-* From the way the datasource is joined, it should also be possible to do joins over different tables 
+* From the way the data source is joined, it should also be possible to do joins over different tables 
   (separate tables with "," in table and add in the WHERE Clauses the table equal joins. 
   This has not been tested!!!)
 
-* It should also be relatively simple to add to the database using the same datasource string.
+* It should also be relatively simple to add to the database using the same data source string.
   This has not been implemented...
 
 * The aggregation functions are ignored and several data columns are used instead