ot;Cameron McBride" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 14, 2002 4:25 PM
Subject: Re: Possible 2.0b7 issues OR Setup help
> > ok, that's good to know
>
> Yeah -- we are sane! ;-)
>
> > Could you please put all the Embperl directive
> >
> > I put this "optEnableChdir" on the TODO list
>
> One problem with the current "no-chdir" behaviour is: when I use
> use Customer::Utils;
> in my Perl code and have the "Customer" directory in the same directory
> where the script is, it does not work anymore.
>
Yes, that's true
> So I ha
Gerald Richter wrote:
>>Understandable -- as this is how I found the optDisableChdir -- looking
>>to turn this function off to increase performance. For functionality
>>however -- could I suggest that you provide some means to 'enable'
>>this? I agree it should be off by default, but it could b
> ok, that's good to know
Yeah -- we are sane! ;-)
> Could you please put all the Embperl directives in the first file and then
> send me the mod_info output for Embperl?
Sure thing.
I made a test that has a configuration that does not work (ie
EMBPERL_OBJECT_BASE does not seem to change in a
>
>
> Well, I found out why my system had nothing for the configuration
> directives via mod_info.
>
> Remember I mentioned that my configurations are separated into different
> files that I 'include' from the httpd.conf. Well, it looks like
> mod_info (at least the version I have) does not follo
Hi!
On Sat, May 11, 2002 at 04:23:18AM -0400, Cameron McBride wrote:
> Remember I mentioned that my configurations are separated into different
> files that I 'include' from the httpd.conf. Well, it looks like
> mod_info (at least the version I have) does not follow these 'include'
> directives,
> > To continue on this, I finally did upgrade my dev machine to 5.6.1, and
> > recompiled mod_perl (1.26). With Embperl 2.0b7 -- the mod_info stats
> > are all still blank. Perhaps it could be a mod_info problem with my
> > set-up -- or some issue with DSOs. ::shrug::
>
> Looks like it has no
Hi Cameron,
thanks for the update...
>
> To continue on this, I finally did upgrade my dev machine to 5.6.1, and
> recompiled mod_perl (1.26). With Embperl 2.0b7 -- the mod_info stats
> are all still blank. Perhaps it could be a mod_info problem with my
> set-up -- or some issue with DSOs. ::
> I don't have any idea why mod_info fails (It reparses the conf file, so it
> may come to different result, then APache itself), but it seems that the
> different Perl version has changed the other thing. I will try to reproduce
> the Perl 5.6.0 here, but this will be not too soon
>
> Did yo
Hi,
> > That would be great! While I don't think it's a kernel isusse, it may
have
> > to do with the Perl version.
>
> Ok, did it. The mod_info part is the same as before (ie pretty much
> blank) -- but the directives inside location blocks work. ;-)
I don't have any idea why mod_info fails (
Heyo,
> > Ayup, thats my setup. I will check it on my production server as well,
> > as it has 5.6.1, a slightly different kernel -- and perhaps a slightly
> > newer version of Apache. Give me a day or two on this one.
>
> That would be great! While I don't think it's a kernel isusse, it may
Hi,
>
> > You have posted you are running Linux 2.4.4 and Perl 5.6.0, right? Maybe
it
> > could be an issue with Perl 5.6.0, but I cannot say that this is the
reason.
>
> Ayup, thats my setup. I will check it on my production server as well, as
it has
> 5.6.1, a slightly different kernel -- and
Heyo,
> You have posted you are running Linux 2.4.4 and Perl 5.6.0, right? Maybe it
> could be an issue with Perl 5.6.0, but I cannot say that this is the reason.
Ayup, thats my setup. I will check it on my production server as well, as it has
5.6.1, a slightly different kernel -- and perhaps a
Hello,
>
> > but when I have to choose, I would always use b7 instead of b5.
>
> OK, I knew some people were using it for prime time, and I just wanted
> to make sure I was not off my rocker for trying to do the same. If its
> good enough for you... ;-)
>
> I finally got a set-up that seems to w
>
> My guess is that Embperl::Object completely controls the directory, and
> EMBPERL_ALLOW restricts the module from using things *before* it can
> determine what to do with a requested component (ie should it not process
> and just serve the .txt file). The EMBPERL_URIMATCH then works in both o
> > > 2. EMBPERL_OBJECT_BASE does not seem to work in my Location pragma
> > > - given the config below, I would just get an error in the
> > > embperl.log about 'kaka.epl' not being found.
> >
> > This looks like the EMBPERL_APPNAME isn't set inside the Location block
> > (Yes, I see it
> Review: .txt --> no processing or restriction
> .htm? --> processing and restriction via the normal expectations
> apache index
> control --> adheres to the EMBPERL_URIMATCH, but not EMBPERL_ALLOW
>
> Perhaps that helps.
I was wrong, setting
EMBPERL_ALLOW (\.htm.?|\.epl$)
i
Thanks for your quick response!
> It's missing in b7, because of the internal changes, but should come in
> again at some point
Great. I would love to get it back... until then, I can live without
it. Its nice to know I'm not blind either...
> > 2. EMBPERL_OBJECT_BASE does not seem to work in
Hi,
>
> 1. What happened to EMBPERL_VIRTLOG???
>(didn't work with PerlSetEnv either)
> - this worked for me with 2.0b5
>
It's missing in b7, because of the internal changes, but should come in
again at some point
> 2. EMBPERL_OBJECT_BASE does not seem to work in my Location pragma
>
Heyo,
First off -- I am new to Embperl, so perhaps I missed a thing or two.
If this is the case, any 'steering' in the right direction would be
appreciated. ;-) I know this is kind of like overload -- so thanks in
advance.
I am trying to put the newest version up in production (yeah, I know
-
20 matches
Mail list logo
