> > But what about the poor user who sticks an unsetenv into their
> > global-scope httpd.conf expecting it to unset a database-related
> > environment variable like ORACLE_HOME or PGHOST or something along those
> > lines such that any Apache module like mod_auth_*, PHP, mod_perl, etc.
> > will not use that env variable. It is somewhat confusing that this works
> > for CGI and mod_include, but nowhere else.
> >
>
> Most likely, the best solution would be to:
>
> env - \
> PATH=/bin \
> HOME=/usr/local/apache \
> /usr/local/apache/httpd .....
>
> or a suitable hacked apachectl or rc.httpd
Yes, but isn't it counter-intuitive to not have unsetenv do this? It
should at the very least be documented that unsetenv doesn't actually
unset an env variable.
-Rasmus
