This patch introduces a feature whereby rrdcached will disallow updates

[rrdtool.git] / doc / rrdthreads.pod

diff --git a/doc/rrdthreads.pod b/doc/rrdthreads.pod
index 7769018..71506e9 100644 (file)
--- a/doc/rrdthreads.pod
+++ b/doc/rrdthreads.pod
@@ -20,26 +20,26 @@ In order to use librrd in multi-threaded programs you must:
 
 =over
 
-=item * 
+=item *
 
 Link with F<librrd_th> instead of F<librrd> (use C<-lrrd_th> when
 linking)
 
-=item * 
+=item *
 
 Use the "C<_r>" functions instead of the normal API-functions
 
-=item * 
+=item *
 
 Do not use any at-style time specifications. Parsing of such time
 specifications is terribly non-thread-safe.
 
-=item * 
+=item *
 
 Never use non *C<_r> functions unless it is explicitly documented that
 the function is tread-safe.
 
-=item * 
+=item *
 
 Every thread SHOULD call C<rrd_get_context()> before its first call to
 any C<librrd_th> function in order to set up thread specific data. This
@@ -126,7 +126,7 @@ C<rrd_update_r> as an example.
 
 =item *
 
-Do not use the C<parsetime> function!
+Do not use the C<rrd_parsetime> function!
 
 It uses lots of global variables. You may use it in functions not designed
 to be thread-safe, like in functions wrapping the C<_r> version of some
@@ -137,7 +137,7 @@ operation (e.g., C<rrd_create>, but not in C<rrd_create_r>)
 =head2 CURRENTLY IMPLEMENTED THREAD SAFE FUNCTIONS
 
 Currently there exist thread-safe variants of C<rrd_update>,
-C<rrd_create>, C<rrd_dump>, C<rrd_info> and C<rrd_last>.
+C<rrd_create>, C<rrd_dump>, C<rrd_info>, C<rrd_last>, and C<rrd_fetch>.
 
 =head1 AUTHOR