Thanks, Haitao! Applied. Cheers, Michael On 03/25/2014 09:24 AM, penght@xxxxxxxxxxxxxx wrote: > The functions random_r(), srandom_r(), initstate_r() and > setstate_r() are thread safe. > > Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> > --- > man3/random_r.3 | 11 ++++++++++- > 1 file changed, 10 insertions(+), 1 deletion(-) > > diff --git a/man3/random_r.3 b/man3/random_r.3 > index 829eb81..92fe430 100644 > --- a/man3/random_r.3 > +++ b/man3/random_r.3 > @@ -23,7 +23,7 @@ > .\" %%%LICENSE_END > .\" > .\" > -.TH RANDOM_R 3 2013-04-19 "GNU" "Linux Programmer's Manual" > +.TH RANDOM_R 3 2014-03-25 "GNU" "Linux Programmer's Manual" > .SH NAME > random_r, srandom_r, initstate_r, setstate_r \- reentrant > random number generator > @@ -125,6 +125,15 @@ or > argument to > .BR random_r () > was NULL. > +.SH ATTRIBUTES > +.SS Multithreading (see pthreads(7)) > +The > +.BR random_r (), > +.BR srandom_r (), > +.BR initstate_r (), > +and > +.BR setstate_r () > +functions are thread-safe. > .SH CONFORMING TO > These functions are nonstandard glibc extensions. > .\" These functions appear to be on Tru64, but don't seem to be on > -- 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
