You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@httpd.apache.org by "William A. Rowe, Jr." <ad...@rowe-clan.net> on 2001/04/05 18:09:47 UTC

Re: setenv/unsetenv?

From: "Rasmus Lerdorf" <ra...@php.net>
Sent: Wednesday, April 05, 2000 8:22 AM


> Could someone remind me of the reason for not having the mod_env
> setenv/unsetenv modify the real environment as well as modifying the
> internal table?
> 
> It is a bit of a hassle to not have an unsetenv in httpd.conf apply to
> directly linked 3rd-party libs that are written to look at the real
> environment with a straight getenv() call.

Sounds hopelessly un-thread-safe

Re: setenv/unsetenv?

Posted by Rasmus Lerdorf <ra...@apache.org>.

> From: "Rasmus Lerdorf" <ra...@php.net>
> Sent: Wednesday, April 05, 2000 8:22 AM
>
>
> > Could someone remind me of the reason for not having the mod_env
> > setenv/unsetenv modify the real environment as well as modifying the
> > internal table?
> >
> > It is a bit of a hassle to not have an unsetenv in httpd.conf apply to
> > directly linked 3rd-party libs that are written to look at the real
> > environment with a straight getenv() call.
>
> Sounds hopelessly un-thread-safe

Yeah well, that's not really an answer for Apache-1.3 on UNIX.  Was there
another reason for not modifying the env directly?

-Rasmus