> EMBPERL_SESSION_HANDLER_CLASS no
>
> ...
>
> REDIRECT_EMBPERL_COMPARTMENT test
> REDIRECT_EMBPERL_DEBUG 0
> REDIRECT_EMBPERL_LOG /www/logs/www.vwrsp.com.embperl.log
> REDIRECT_EMBPERL_OPTIONS 1024
> REDIRECT_EMBPERL_SESSION_HANDLER_CLASS no
>
> When I look at that, it says t
EDIRECT_EMBPERL_COMPARTMENT test
REDIRECT_EMBPERL_DEBUG 0
REDIRECT_EMBPERL_LOG /www/logs/www.vwrsp.com.embperl.log
REDIRECT_EMBPERL_OPTIONS 1024
REDIRECT_EMBPERL_SESSION_HANDLER_CLASS no
When I look at that, it says to me that Embperl logging should be off. I've
reloaded the page a lot, and haven't seen
Thanks to everyone for the replies. I'll get to them all, but I can answer
Sherman Culler's questions now.
>Just curious - why not upgrade Apache/Embperl/mod_perl to the latest
>versions - Apache 2.x, Embperl 2.x and mod_perl 2?
We tried this a while ago. Embperl 2 is stricter with its HTML val
d
> noticed that Embperl seems to be logging "everything." So much stuff that
> we have to truncate them every hour or so.
>
> Below is a snippet from one of our httpd.conf files, which contains the
> embperl directives. It looks like this was intended to shut off Embperl
>
directives. It looks like this was intended to shut off Embperl
logging, but it's not working. I've tried to debug this, for instance by
using PerlSetEnv to set the variables, or setting EMBPERL_DEBUG to 1. The
only thing that's been effective so far is setting the EMBPERL_LOG to
Gerald Richter wrote:
> > [1175]ERR: 24: Line 3: Error in Perl code: Recursive inheritance
> > detected while looking for method 'get_tour' in package
> > 'HTML::Embperl::DOC::_3' at
> > /www/crazyguyonabike/com/htdocs/journal/contents/init.html line 13.
> >
>
> I have fixed this also in the cur
Neil,
>
> [1175]ERR: 24: Line 3: Error in Perl code: Recursive inheritance
> detected while looking for method 'get_tour' in package
> 'HTML::Embperl::DOC::_3' at
> /www/crazyguyonabike/com/htdocs/journal/contents/init.html line 13.
>
I have fixed this also in the current CVS version. This was d
>
> It is defined as a constant:
>
> *bgcolor = \"beige";
>
> This is the way to do constants which I read about in the Programming
> Perl book...
Never saw this before, but it really defines a constant. The problem is from
within Perl I don't see any chance to catch the difference between such a
> > The last message is weird. The variable concerned is a constant, which
> > should never be changed. There are many other constants which I defined,
> > so I am not sure why this one should cause a problem. I have checked my
> > code and it is used 3 times, in different files, in very simple
>
>
> [2772]CUP: Error while cleanup $HTML::Embperl::DOC::_1::page_bgcolor:
> Modification of a read-only value attempted at
> /usr/lib/perl5/site_perl/5.6.0/i386-linux/HTML/Embperl.pm line 1393.
>
> The "processblock" stuff looks a lot like the logging which you added to
> epmain.c when we were tr
> > Yes, in the CVS version there sometimes some extra logging. To turn all
> > logging off, just set
> >
> > PerlSetEnv EMBPERL_LOGFILE /dev/null
> >
> > I normaly remove this extra logging before I release a new version.
>
> I tried putting this line in my production server httpd.conf, but I am
> > I am using the CVS latest version currently, because it seems to have
> > the latest fix which you made to EmbperlObject as a result of all those
> > problems I was having. It's working great, but I notice that I am still
> > getting a lot of debug logging into /tmp/embperl.log, even with
> >
Neil,
>
> I am using the CVS latest version currently, because it seems to have
> the latest fix which you made to EmbperlObject as a result of all those
> problems I was having. It's working great, but I notice that I am still
> getting a lot of debug logging into /tmp/embperl.log, even with
> E
13 matches
Mail list logo
