B<rrdtool> {B<update> | B<updatev>} I<filename>
S<[B<--template>|B<-t> I<ds-name>[B<:>I<ds-name>]...]>
S<[B<--daemon>|B<-d> I<address>]> [B<-->]
-S<B<N>|I<timestamp>B<:>I<value>[B<:>I<value>...]>
-S<I<at-timestamp>B<@>I<value>[B<:>I<value>...]>
-S<[I<timestamp>B<:>I<value>[B<:>I<value>...] ...]>
+S<{{B<N> | I<timestamp>}B<:> | I<at-timestamp>B<@>}I<value>[B<:>I<value>]... ...>
=head1 DESCRIPTION
using the template switch), B<RRDtool> will ignore the value specified
for the COMPUTE B<DST>.
+The caching daemon L<rrdcached> cannot be used together with templates yet.
+
=item B<--skip-past-updates>
When updateing an rrd file with data earlier than the latest update already
=item B<--daemon>|B<-d> I<address>
If given, B<RRDTool> will try to connect to the caching daemon L<rrdcached>
-at I<address> and will fail if the connection cannot be established. If the
-connection is successfully established the values will be sent to the daemon
-instead of accessing the files directly.
+at I<address>. If the connection is successfully established the values will
+be sent to the daemon instead of accessing the files directly. If the
+connection cannot be established it will fall back to direct file-access.
+While this is convenient, it can silently create problems so please read
+the warning in the examples.
For a list of accepted formats, see the B<-l> option in the L<rrdcached> manual.
-=item B<N>|I<timestamp>B<:>I<value>[B<:>I<value>...]
+=item {B<N> | I<timestamp>}B<:>I<value>[B<:>I<value>]...
The data used for updating the RRD was acquired at a certain
time. This time can either be defined in seconds since 1970-01-01 or
=item *
-C<rrdtool update --cache /var/lib/rrd/demo3.rrd N:42>
-
-Update the file C</var/lib/rrd/demo3.rrd> with a single data source, using the
-current time. If the caching daemon cannot be reached, do B<not> fall back to
-direct file access.
-
-=item *
-
C<rrdtool update --daemon unix:/tmp/rrdd.sock demo4.rrd N:23>
Use the UNIX domain socket C</tmp/rrdd.sock> to contact the caching daemon. If