X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=doc%2Frrdfetch.pod;h=7ebd9d603bb84dc0705f0c2a621fb6343b03be48;hb=796072efc3e448842c4cef975bc21ae540cd7635;hp=6eb10d140921bb768ecac32159a9dd09e402fed0;hpb=4b7345f9345915c8061e4b37b26ce8887828c973;p=rrdtool.git

diff --git a/doc/rrdfetch.pod b/doc/rrdfetch.pod
index 6eb10d1..7ebd9d6 100644
--- a/doc/rrdfetch.pod
+++ b/doc/rrdfetch.pod
@@ -4,10 +4,10 @@ rrdfetch - Fetch data from an RRD.
 
 =head1 SYNOPSIS
 
-B<rrdtool> B<fetch> I<filename> I<CF> 
-S<[B<--resolution>|B<-r> I<resolution>]> 
-S<[B<--start>|B<-s> I<start>]> 
-S<[B<--end>|B<-e> I<end>]> 
+B<rrdtool> B<fetch> I<filename> I<CF>
+S<[B<--resolution>|B<-r> I<resolution>]>
+S<[B<--start>|B<-s> I<start>]>
+S<[B<--end>|B<-e> I<end>]>
 
 =head1 DESCRIPTION
 
@@ -20,11 +20,11 @@ function.
 
 =over 8
 
-=item I<filename> 
+=item I<filename>
 
 the name of the B<RRD> you want to fetch the data from.
 
-=item I<CF> 
+=item I<CF>
 
 the consolidation function that is applied to the data you
 want to fetch (AVERAGE,MIN,MAX,LAST)
@@ -52,8 +52,8 @@ specify the end time.
 
 =head2 RESOLUTION INTERVAL
 
-In order to get RRDtool to fetch anything other than the finest resolution RRA 
-B<both> the start and end time must be specified on boundaries that are 
+In order to get RRDtool to fetch anything other than the finest resolution RRA
+B<both> the start and end time must be specified on boundaries that are
 multiples of the desired resolution. Consider the following example:
 
  rrdtool create subdata.rrd -s 10 DS:ds0:GAUGE:300:0:U \
@@ -92,10 +92,10 @@ both start and end time are within the desired RRA
 
 =back
 
-So, if time now is called "t", do 
+So, if time now is called "t", do
 
  end time == int(t/900)*900,
- start time == end time - 1hour, 
+ start time == end time - 1hour,
  resolution == 900.
 
 Using the bash shell, this could look be:
@@ -135,14 +135,12 @@ or just B<HH>. You can suffix it with B<am> or B<pm> or use
 including B<midnight> (00:00), B<noon> (12:00) and British
 B<teatime> (16:00).
 
-=for comment
-XXX Wouldn't it be nice to have z'N\"uni and z'Vieri for Switzerland?
-
-The I<day> can be specified as I<month-name> I<day-of-the-month>
-and optional a 2- or 4-digit I<year> number (e.g. March 8 1999).
-Alternatively, you can use I<day-of-week-name> (e.g. Monday),
-or one of the words: B<yesterday>, B<today>, B<tomorrow>.
-You can also specify the I<day> as a full date in several numerical formats, including B<MM/DD/[YY]YY>, B<DD.MM.[YY]YY>, or B<YYYYMMDD>.
+The I<day> can be specified as I<month-name> I<day-of-the-month> and
+optional a 2- or 4-digit I<year> number (e.g. March 8 1999). Alternatively,
+you can use I<day-of-week-name> (e.g. Monday), or one of the words:
+B<yesterday>, B<today>, B<tomorrow>. You can also specify the I<day> as a
+full date in several numerical formats, including B<MM/DD/[YY]YY>,
+B<DD.MM.[YY]YY>, or B<YYYYMMDD>.
 
 I<NOTE1>: this is different from the original at(1) behavior, where a
 single-number date is interpreted as MMDD[YY]YY.