On 12/31/2014 06:22 AM, Ma Shimiao wrote:
> The function setenv() and unsetenv() are thread unsafe.
Thanks, Ma Shimiao. Applied in my local branch.
Cheers,
Michael
> Signed-off-by: Ma Shimiao <mashimiao.fnst@xxxxxxxxxxxxxx>
> ---
> man3/setenv.3 | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/man3/setenv.3 b/man3/setenv.3
> index 6683d59..e28bf0d 100644
> --- a/man3/setenv.3
> +++ b/man3/setenv.3
> @@ -125,6 +125,19 @@ or contains an \(aq=\(aq character.
> .TP
> .B ENOMEM
> Insufficient memory to add a new variable to the environment.
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lb lb lb
> +l l l.
> +Interface Attribute Value
> +T{
> +.BR setenv (),
> +.BR unsetenv ()
> +T} Thread safety MT-Unsafe const:env
> +.TE
> .SH CONFORMING TO
> 4.3BSD, POSIX.1-2001.
> .SH NOTES
>
--
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
