putenv.3: Remove ancient Linux libc details

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-06-29 15:44:04 +02:00
parent 07fc376582
commit 99c4073b93
1 changed files with 13 additions and 13 deletions

View File

@ -83,19 +83,19 @@ The
.BR putenv ()
function is not required to be reentrant, and the
one in glibc 2.0 is not, but the glibc 2.1 version is.
.LP
Description for libc4, libc5, glibc:
If the argument \fIstring\fP is of the form \fIname\fP,
and does not contain an \(aq=\(aq character, then the variable \fIname\fP
is removed from the environment.
If
.BR putenv ()
has to allocate a new array \fIenviron\fP,
and the previous array was also allocated by
.BR putenv (),
then it will be freed.
In no case will the old storage associated
to the environment variable itself be freed.
.\" .LP
.\" Description for libc4, libc5, glibc:
.\" If the argument \fIstring\fP is of the form \fIname\fP,
.\" and does not contain an \(aq=\(aq character, then the variable \fIname\fP
.\" is removed from the environment.
.\" If
.\" .BR putenv ()
.\" has to allocate a new array \fIenviron\fP,
.\" and the previous array was also allocated by
.\" .BR putenv (),
.\" then it will be freed.
.\" In no case will the old storage associated
.\" to the environment variable itself be freed.
.LP
The libc4 and libc5 and glibc 2.1.2 versions conform to SUSv2:
the pointer \fIstring\fP given to