Applied. Thanks. On 02/18/2014 10:26 AM, Peng Haitao wrote: > The functions setbuf(), setbuffer(), setlinebuf() and setvbuf() > are thread safe. > > Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> > --- > man3/setbuf.3 | 11 ++++++++++- > 1 file changed, 10 insertions(+), 1 deletion(-) > > diff --git a/man3/setbuf.3 b/man3/setbuf.3 > index ad9914f..242afcf 100644 > --- a/man3/setbuf.3 > +++ b/man3/setbuf.3 > @@ -45,7 +45,7 @@ > .\" Correction, 2000-03-03, Andreas Jaeger <aj@xxxxxxx> > .\" Added return value for setvbuf, aeb, > .\" > -.TH SETBUF 3 2012-08-03 "Linux" "Linux Programmer's Manual" > +.TH SETBUF 3 2014-02-18 "Linux" "Linux Programmer's Manual" > .SH NAME > setbuf, setbuffer, setlinebuf, setvbuf \- stream buffering operations > .SH SYNOPSIS > @@ -161,6 +161,15 @@ It may set > on failure. > > The other functions do not return a value. > +.SH ATTRIBUTES > +.SS Multithreading (see pthreads(7)) > +The > +.BR setbuf (), > +.BR setbuffer (), > +.BR setlinebuf (), > +and > +.BR setvbuf () > +functions are thread-safe. > .SH CONFORMING TO > The > .BR setbuf () > -- 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
