X-Git-Url: https://git.verplant.org/?a=blobdiff_plain;f=doc%2Frrdgraph.pod;h=2c57dbb156b7e1687e8f04916273bf2cb05e3de2;hb=a12627275ff8487174cbb907a066f62a00b6ae44;hp=4e911c056e61fc1447b3b3401ce9f91c43cbef5c;hpb=6836df3d35177c87c3d03e0c622d738305bd390c;p=rrdtool.git
diff --git a/doc/rrdgraph.pod b/doc/rrdgraph.pod
index 4e911c0..2c57dbb 100644
--- a/doc/rrdgraph.pod
+++ b/doc/rrdgraph.pod
@@ -248,7 +248,7 @@ to the more robust B<--alt-y-grid> mode.
How many digits should rrdtool assume the y-axis labels to be? You
may have to use this option to make enough space once you start
-fideling with the y-axis labeling.
+fiddling with the y-axis labeling.
[B<--units=si>]
@@ -267,6 +267,17 @@ Note, that only the image size will be returned, if you run with lazy even
when using graphv and even when using PRINT.
+[B<--daemon> I
]
+
+Address of the L daemon. If specified, a C command is sent
+to the server before reading the RRD files. This allows the graph to contain
+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, see example below. Other
+addresses are interpreted as normal network addresses, i.Ee. IPv4 or IPv6
+addresses in most cases.
+
+ rrdtool graph [...] --daemon unix:/var/run/rrdcached.sock [...]
+
[B<-f>|B<--imginfo> I]
After the image has been created, the graph function uses printf
@@ -285,7 +296,7 @@ I is one of C background, C