After research, We think
* rresvport(),
* iruserok(),
* ruserok(),
* rresvport_af(),
* iruserok_af(),
* ruserok_af(),
are thread-safe. And
* rcmd(),
* rcmd_af(),
are not thread-safe. But, there are not
markings of them in glibc document.
Signed-off-by: Zeng Linggang <zenglg.jy@xxxxxxxxxxxxxx>
---
man3/rcmd.3 | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/man3/rcmd.3 b/man3/rcmd.3
index 7bc7313..64feb53 100644
--- a/man3/rcmd.3
+++ b/man3/rcmd.3
@@ -267,6 +267,30 @@ The functions
and
.BR ruserok_af ()
functions are provide in glibc since version 2.2.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw17 lb lb
+l l l.
+Interface Attribute Value
+T{
+.BR rcmd (),
+.BR rcmd_af ()
+T} Thread safety MT-Unsafe
+T{
+.BR rresvport (),
+.BR rresvport_af ()
+T} Thread safety MT-Safe
+T{
+.BR iruserok (),
+.BR ruserok (),
+.BR iruserok_af (),
+.BR ruserok_af ()
+T} Thread safety MT-Safe locale
+.TE
+
.SH CONFORMING TO
Not in POSIX.1-2001.
Present on the BSDs, Solaris, and many other systems.
--
1.9.3
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
