From d17a566b1ecd2c1fe07b846aa6720f874f3ab12d Mon Sep 17 00:00:00 2001
From: Bruno Haible <bruno@clisp.org>
Date: Mon, 19 Sep 2005 15:47:27 +0000
Subject: [PATCH] Note about inet_ntoa.

---
 doc/inet_ntoa.texi | 13 +++++++++++++
 1 file changed, 13 insertions(+)
 create mode 100644 doc/inet_ntoa.texi

diff --git a/doc/inet_ntoa.texi b/doc/inet_ntoa.texi
new file mode 100644
index 000000000..e4ecda22f
--- /dev/null
+++ b/doc/inet_ntoa.texi
@@ -0,0 +1,13 @@
+@node inet_ntoa
+@section inet_ntoa
+@findex inet_ntoa
+
+The @code{inet_ntoa} function need not be reentrant, and consequently
+is not required to be thread safe.  Implementations of
+@code{inet_ntoa} typically write the time stamp into static buffer.
+If two threads call @code{inet_ntoa} at roughly the same time, you
+might end up with the wrong date in one of the threads, or some
+undefined string.  Further, @code{inet_ntoa} is specific for
+@acronym{IPv4} addresses.
+
+A protocol independent function is @code{inet_ntop}.
-- 
2.11.0