As annotation in glibc manual is more detailed, change the
thread-safety information to be the same as glibc manual.
Signed-off-by: Ma Shimiao <mashimiao.fnst@xxxxxxxxxxxxxx>
---
man3/getlogin.3 | 29 +++++++++++++++++++++++++++--
1 file changed, 27 insertions(+), 2 deletions(-)
diff --git a/man3/getlogin.3 b/man3/getlogin.3
index 828df2b..241f81c 100644
--- a/man3/getlogin.3
+++ b/man3/getlogin.3
@@ -147,14 +147,39 @@ l l l.
Interface Attribute Value
T{
.BR getlogin ()
-T} Thread safety MT-Unsafe locale
+T} Thread safety T{
+MT-Unsafe race:getlogin race:utent
+.br
+sig:ALRM timer locale
+T}
T{
.BR getlogin_r ()
-T} Thread safety MT-Safe locale
+T} Thread safety T{
+MT-Unsafe race:utent sig:ALRM timer
+.br
+locale
+T}
T{
.BR cuserid ()
T} Thread safety MT-Unsafe race:cuserid/!string locale
.TE
+
+[[
+In the above table,
+.I utent
+in
+.I race:utent
+signifies that if any of the functions
+.BR setutent (),
+.BR getutent (),
+or
+.BR endutent ()
+are used in parallel in different threads of a program, then data races could occur.
+.BR getlogin ()
+and
+.BR getlogin_r ()
+call them, so we use race:utent to remind users.
+]]
.SH CONFORMING TO
.BR getlogin ()
and
--
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
