rcmd.3: ATTRIBUTES: Note functions that are/aren't thread-safe

After research, We think
* rresvport(),
* iruserok(),
* ruserok(),
* rresvport_af(),
* iruserok_af(),
* ruserok_af(),
are thread-safe. And
* rcmd(),
* rcmd_af(),
are not thread-safe. But, there are not
markings of them in glibc document.

Signed-off-by: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Zeng Linggang 2015-06-11 10:04:28 +08:00 committed by Michael Kerrisk
parent 44518c2d1d
commit e196c9004e
1 changed files with 24 additions and 0 deletions

View File

@ -267,6 +267,30 @@ The functions
and
.BR ruserok_af ()
functions are provide in glibc since version 2.2.
.SH ATTRIBUTES
For an explanation of the terms used in this section, see
.BR attributes (7).
.TS
allbox;
lbw17 lb lb
l l l.
Interface Attribute Value
T{
.BR rcmd (),
.BR rcmd_af ()
T} Thread safety MT-Unsafe
T{
.BR rresvport (),
.BR rresvport_af ()
T} Thread safety MT-Safe
T{
.BR iruserok (),
.BR ruserok (),
.BR iruserok_af (),
.BR ruserok_af ()
T} Thread safety MT-Safe locale
.TE
.SH CONFORMING TO
Not in POSIX.1-2001.
Present on the BSDs, Solaris, and many other systems.