> -----Original Message-----
> From: Mark Doyle [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 15, 2000 4:06 PM
> To: Jimi Thompson
> Cc: [EMAIL PROTECTED]
> Subject: Re: Apache::Reload and environment variables
>
>
>
> On Friday, December 15, 2000, at 04:01 PM, Jimi Thompson wrote:
>
> > If the variable ORACLE_HOME doesn't change why not just set
> it as an
> > environment variable outside the program and export it?
>
> >> PerlSetEnv ORACLE_HOME /oracle/app/oracle/product/8.0.3/
> >> PerlModule Apache::DBI
> >> [...]
> >> PerlModule Apache::Reload
> >> PerlInitHandler Apache::Reload
> >> PerlSetVar ReloadAll Off
>
> That snippet is from my httpd.conf file - it is globally
> defined there. Isn't that the same as what you are saying?
well, it's not the same - what he means is for you to export ORACLE_HOME in
/etc/passwd or somesuch
DBD::Oracle needs ORACLE_HOME set at compile time - for Registry scripts its
ok to PerlSetEnv so that when your .cgi use()s DBD::Oracle, it's there...
for handlers, though, PerlSetEnv may be too late, especially if you are
using a startup.pl script. generally what I do is to use a BEGIN block in
startup.pl to define ORACLE_HOME prior to using Apache::DBI, DBI, and
DBD::Oracle. if you export it from /etc/profile then you probably don't
need to do this (but it can't hurt, either - I do both)
I don't know specifically why Apache::Reload is causing this behavior, but
try the above and see if that clears things up...
HTH
--Geoff
>
> Cheers,
> Mark
>
