X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=doc%2Frrdgraph_data.pod;h=dba53f3720a4a302b2cc8651545eed3a993bbd89;hb=9b8a8e557d4c271ad4efe95c4b7bb7f0803e729c;hp=975c385d783733acf906d4d4b2e15f21165b390d;hpb=4b7345f9345915c8061e4b37b26ce8887828c973;p=rrdtool.git diff --git a/doc/rrdgraph_data.pod b/doc/rrdgraph_data.pod index 975c385..dba53f3 100644 --- a/doc/rrdgraph_data.pod +++ b/doc/rrdgraph_data.pod @@ -19,6 +19,9 @@ useful information such as maximum, minimum etcetera. Two of the instructions use a language called B which is described in its own manual page. +Variable names (I) must be made up strings of the following characters +C, starting with a letter and a maximum length of 255 characters. + =head1 DEF BIvnameE>=IrrdfileE>:Ids-nameE>:ICFE>[:step=IstepE>][:start=ItimeE>][:end=ItimeE>][:reduce=IBE>] @@ -27,7 +30,7 @@ This command fetches data from an B file. The virtual name I can then be used throughout the rest of the script. By default, an B which contains the correct consolidated data at an appropriate resolution will be chosen. The resolution can -be overridden with the L<--step|rrdgraph/item_Time> option. +be overridden with the L<--step|rrdgraph/item_Time> option. The resolution can again be overridden by specifying the B. The time span of this data is the same as for the graph by default, you can override this by specifying B. Remember to @@ -41,8 +44,6 @@ from an B. For instance, if your B has an B with a resolution of 1800 seconds per B, you should create an image with width 400 and time span 400*1800 seconds (use appropriate start and end times, such as C<--start end-8days8hours>). -=for comment -XXX is the above start/end syntax correct? Fritz If consolidation needs to be done, the B of the B specified in the B itself will be used to reduce the data density. This behaviour can