use snprintf, strdup, ... where possible to make for safer operation -- Martin Pelikan

[rrdtool.git] / doc / rrdxport.pod

diff --git a/doc/rrdxport.pod b/doc/rrdxport.pod
index 11159e4..bf9fd52 100644 (file)
--- a/doc/rrdxport.pod
+++ b/doc/rrdxport.pod
@@ -9,6 +9,7 @@ S<[B<-s>|B<--start> I<seconds>]>
 S<[B<-e>|B<--end> I<seconds>]>
 S<[B<-m>|B<--maxrows> I<rows>]>
 S<[B<--step> I<value>]>
+S<[B<--json>]>
 S<[B<--daemon> I<address>]>
 S<[B<DEF:>I<vname>B<=>I<rrd>B<:>I<ds-name>B<:>I<CF>]>
 S<[B<CDEF:>I<vname>B<=>I<rpn-expression>]>
@@ -53,14 +54,16 @@ See L<rrdgraph> documentation.
 
 Address of the L<rrdcached> daemon. If specified, a C<flush> command is sent
 to the server before reading the RRD files. This allows B<rrdtool> to return
-fresh data even if the daemon is configured to cache values for a long time. To
-specify a UNIX domain socket use the prefix C<unix:>, see example below. Other
-addresses are interpreted as normal network addresses, i.E<nbsp>e. IPv4 or IPv6
-addresses in most cases.
+fresh data even if the daemon is configured to cache values for a long time.
+For a list of accepted formats, see the B<-l> option in the L<rrdcached> manual.
 
- rrdtool xport --daemon unix:/var/run/rrdcached.sock ...
+  rrdtool xport --daemon unix:/var/run/rrdcached.sock ...
 
-=item B<--enumds> 
+=item B<--json>
+
+produce json formated output (instead of xml)
+
+=item B<--enumds>
 
 The generated xml should contain the data values in enumerated tags.