From a041475c7d6631ce9d35cb53476bc956b4890c89 Mon Sep 17 00:00:00 2001
From: oetiker <oetiker@a5681a0c-68f1-0310-ab6d-d61299d08faa>
Date: Sat, 22 Feb 2003 21:57:35 +0000
Subject: [PATCH] Initial checkin -- Peter Stamfest <peter@stamfest.at>

git-svn-id: svn://svn.oetiker.ch/rrdtool/trunk@187 a5681a0c-68f1-0310-ab6d-d61299d08faa
---
 program/doc/rrdthreads.pod | 150 +++++++++++++++++++++++++++++++++++++
 1 file changed, 150 insertions(+)
 create mode 100644 program/doc/rrdthreads.pod

diff --git a/program/doc/rrdthreads.pod b/program/doc/rrdthreads.pod
new file mode 100644
index 00000000..7e6a6895
--- /dev/null
+++ b/program/doc/rrdthreads.pod
@@ -0,0 +1,150 @@
+=head1 NAME
+
+ rrdthreads - Provisions for linking the RRD library to use in multi-threaded programs
+
+=head1 SYNOPSIS
+
+Using librrd in multi-threaded programs requires some extra
+precautions, as the RRD library in its original form was not
+thread-safe at all. This document describes requirements and pitfalls
+on the way to use the multi-threaded version of librrd in your own
+programs. It also gives hints for future RRD development to keep the
+library thread-safe..
+
+Currently only some RRD operations are implemented in a thread-safe
+way. They all end in the usual "C<_r>" prefix.
+
+=head1 DESCRIPTION
+
+In order to use the librrd in multi-threaded programs you must:
+
+=over 4
+
+=item * 
+
+Link with F<librrd_th> instead of with F<librrd> (use C<-lrrd_th> when
+linking)
+
+=item * 
+
+Use the "C<_r>" functions instead or the normal API-functions
+
+=item * 
+
+Do not use any at-style time specifications. Parsing of such time
+specifications is terribly non-thread-safe.
+
+=item * 
+
+Never use non *C<_r> functions unless it is explicitly documented that
+the function is tread-safe
+
+=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
+is not strictly required, but it is the only way to test if memory
+allocation can be done by this function. Otherwise the program may die
+with a SIGSEGV in a low-memory situation.
+
+=item *
+
+Always call C<rrd_error_clear()> before any call to the
+library. Otherwise the call might fail due to some earlier error.
+
+=back
+
+=head1 IMPORTANT NOTES FOR RRD CONTRIBUTORS:
+
+Some precautions must be followed when developing RRD from now on:
+
+=over 4
+
+=item *
+
+Only use thread-safe functions in library code. Many often used libc
+functions aren't thread-safe. Take care in the following
+situations/when using the following library functions:
+
+=over 8
+
+=item *
+
+Direct calls to C<strerror()> must be avoided: use C<rrd_strerror()>
+instead, it provides a per-thread error message.
+
+=item *
+
+The C<getpw*>, C<getgr*>, C<gethost*> function families (and some more
+C<get*> functions) are not thread-safe: use the *C<_r> variants
+
+=item *
+
+Time functions: C<asctime>, C<ctime>, C<gmtime>, C<localtime>: use
+*C<_r> variants
+
+=item *
+
+C<strtok>: use C<strtok_r>
+
+=item *
+
+C<tmpnam>: use C<tmpnam_r>
+
+=item *
+
+Many other (lookup documentation)
+
+=back
+
+As an aide(?) a header file named F<rrd_is_thread_safe.h> is provided
+that works with the GNU C-preprocessor to "poison" some of the most
+common non-thread-safe functions using the C<#pragma GCC poison>
+directive. Just include this header in source files you want to keep
+thread-safe.
+
+=item *
+
+Do not introduce global variables!
+
+If you really, really have to use a global variable you may add a new
+field to the C<rrd_context> structure and modify F<rrd_error.c>,
+F<rrd_thread_safe.c> and F<rrd_non_thread_safe.c>
+
+=item *
+
+Do not use C<getopt> or C<getopt_long> in *C<_r> (directly or
+indirectly)
+
+C<getopt> uses global variables and behaves badly in a multithreaded
+application when called concurrently. Instead provide a *_r function
+taking all options as function parameters. You may provide argc and
+**argv arguments for variable length argument lists. See
+C<rrd_update_r> as an example.
+
+=item *
+
+Do not use the C<parsetime> function!
+
+It uses lots of global vars. You may use it in functions not designed
+to be thread-safe like functions wrapping the C<_r> version of some
+operation (eg. C<rrd_create>, but not in C<rrd_create_r>)
+
+=back
+
+=head1 CURRENTLY IMPLEMENTED THREAD SAFE FUNCTIONS
+
+Currently there exit thread-safe variants of C<rrd_update>,
+C<rrd_create>, C<rrd_dump>, C<rrd_info> and C<rrd_last>.
+
+=head1 AUTHOR
+
+Initial multi-threading support was implemented by Peter Stamfest
+<peter@stamfest.at> in Feb. 2003.
+
+This documentation was written by Peter Stamfest.
+
+Changes to the RRD library and this documentation are (c) 2003 by
+Peter Stamfest and are distributed under the GPL.
+
+=cut
-- 
2.30.2