Thanks, Haitao. Applied. Cheers, Michael On 04/08/2014 07:57 AM, Peng Haitao wrote: > The functions getutmp() and getutmpx() are thread safe. > > Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> > --- > man3/getutmp.3 | 9 ++++++++- > 1 file changed, 8 insertions(+), 1 deletion(-) > > diff --git a/man3/getutmp.3 b/man3/getutmp.3 > index 4c5e366..35f2124 100644 > --- a/man3/getutmp.3 > +++ b/man3/getutmp.3 > @@ -23,7 +23,7 @@ > .\" the source, must acknowledge the copyright and authors of this work. > .\" %%%LICENSE_END > .\" > -.TH GETUTMP 3 2014-03-09 "Linux" "Linux Programmer's Manual" > +.TH GETUTMP 3 2014-04-08 "Linux" "Linux Programmer's Manual" > .SH NAME > getutmp, getutmpx \- copy utmp structure to utmpx, and vice versa > .SH SYNOPSIS > @@ -52,6 +52,13 @@ function performs the converse operation. > These functions do not return a value. > .SH VERSIONS > These functions first appeared in glibc in version 2.1.1. > +.SH ATTRIBUTES > +.SS Multithreading (see pthreads(7)) > +The > +.BR getutmp () > +and > +.BR getutmpx () > +functions are thread-safe. > .SH CONFORMING TO > These functions are nonstandard, but appear on a few other systems, > such as Solaris and NetBSD. > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- 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
