the issue is that environ[] is not thread safe. so mod_perl2 unties %ENV from the underlying environ[] array under the perl-script handler. i assume the oracle driver or client library uses getenv() (which fetches from the environ[] array). when %ENV is untied from environ[], perl-land will see %ENV changes, but C-land will not see the coresponding changes in environ[]. the 'modperl' handler does not untie %ENV from environ[].
so, one should avoid setting %ENV values whenever possible. and if it is required, should be done at startup time. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
