> OK, I've switched everything over to using SetEnv, and I'm still not
> getting the behavior I expect. In particular, the Log file is being
> written to /tmp, even though I have it set to go elsewhere as you can
> see form the SetEnv below.
>

Embperl_log must be set before Embperl is loaded (same for the session
stuff).

I guess you have a PerlModule HTML::EMbperl somewhere before. Try to change
the order

Gerald

P.S. Please keep the discussion on the list

> > <VirtualHost ...>
> >       .
> >       .
> >       .
> >   AddType text/html .epl
> >   SetEnv EMBPERL_LOG /var/www/domains/mc/embperl_log
> >   SetEnv EMBPERL_DEBUG 0
> >   #SetEnv EMBPERL_DEBUG 2285
> >   SetEnv EMBPERL_SESSION_CLASSES "MySQL Semaphore"
> >   SetEnv EMBPERL_SESSION_ARGS "DataSource=DBI:mysql:database..."
> >
> >   <Files *.epl>
> >         SetHandler      perl-script
> >         Perlhandler     HTML::Embperl
> >         Options         ExecCGI
> >   </files>
> > </VirtualHost>
> >
> The weird thing, is that the EMBPERL_DEBUG variable does seem to be
> working. If I change the debug level from 0 and restart Apache, more
> stuff get's logged as one would expect. The others though seem to be
> simply ignored. Am I missing something?
>
> Something else weird is that the following error is showing up in the
> log twice for every embperl page that is called for a web browser,
> irrespective of the value of EMBPERL_DEBUG:
> > [26364]CUP:  Error while closing HTML::Embperl::DOC::_1::LOG: Can't
> > locate object method "CLOSE" via package "HTML::Embperl::Log" at
> > /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/HTML/Embperl.pm
> > line 1447.
>
> Not sure if it's relevant.
>
> Any clues? Thanks.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to