On 07/23/13 04:25, Peng Haitao wrote: > The functions flockfile(), ftrylockfile() and funlockfile() are > thread safe. Thanks. Applied. Cheers, Michael > Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> > --- > man3/flockfile.3 | 10 +++++++++- > 1 file changed, 9 insertions(+), 1 deletion(-) > > diff --git a/man3/flockfile.3 b/man3/flockfile.3 > index 5f1a1f6..0989038 100644 > --- a/man3/flockfile.3 > +++ b/man3/flockfile.3 > @@ -22,7 +22,7 @@ > .\" the source, must acknowledge the copyright and authors of this work. > .\" %%%LICENSE_END > .\" > -.TH FLOCKFILE 3 2008-08-29 "" "Linux Programmer's Manual" > +.TH FLOCKFILE 3 2013-07-23 "" "Linux Programmer's Manual" > .SH NAME > flockfile, ftrylockfile, funlockfile \- lock FILE for stdio > .SH SYNOPSIS > @@ -124,6 +124,14 @@ function returns zero for success > (the lock was obtained), and nonzero for failure. > .SH ERRORS > None. > +.SH ATTRIBUTES > +.SS Multithreading (see pthreads(7)) > +The > +.BR flockfile (), > +.BR ftrylockfile (), > +and > +.BR funlockfile () > +functions are thread-safe. > .SH CONFORMING TO > POSIX.1-2001. > .SH AVAILABILITY > -- 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
