After research, We think
* setaliasent(),
* endaliasent(),
* getaliasent_r(),
* getaliasbyname_r(),
are thread-safe. And
* getaliasent(),
* getaliasbyname(),
are not thread-safe. But, there are not
markings of them in glibc document.
Signed-off-by: Zeng Linggang <zenglg.jy@xxxxxxxxxxxxxx>
---
man3/setaliasent.3 | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/man3/setaliasent.3 b/man3/setaliasent.3
index d78fd43..c8dd7d3 100644
--- a/man3/setaliasent.3
+++ b/man3/setaliasent.3
@@ -98,6 +98,26 @@ The default alias database is the file
This can be changed in the
.I /etc/nsswitch.conf
file.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw19 lb lb
+l l l.
+Interface Attribute Value
+T{
+.BR setaliasent (),
+.BR endaliasent (),
+.BR getaliasent_r (),
+.BR getaliasbyname_r ()
+T} Thread safety MT-Safe locale
+T{
+.BR getaliasent (),
+.BR getaliasbyname ()
+T} Thread safety MT-Unsafe
+.TE
+
.SH CONFORMING TO
These routines are glibc-specific.
The NeXT system has similar routines:
--
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
