> From: "Rasmus Lerdorf" <[EMAIL PROTECTED]>
> 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