>
> i see, 1.x had logic in perl_util.c:perl_clear_env to leave TZ and PATH in
> %ENV. just committed a change that will do that same, making $ENV{PATH}
> available at startup.
>
Works now for me without the need of PerlPassEnv PATH
Thanks
Gerald
-
>> I fixed that by "aliasing" Apache::log_error to Apache->server->log_error, by
>> adding "sub Apache::log_error" to <...where-perl-lives>/Apache2/Apache/compat.pm.
>
>ok, we can do the same (or similar) in compat.pm to support
>Apache::log_error
thanks.
>> However, more complex code will sti
I was documenting the env vars set under 2.0, and saw that
GATEWAY_INTERFACE shouldn't be available under 2.0 unless MP_COMPAT_1X
is defined. But it's always defined. What's the plan?
__
Stas BekmanJAm_pH --> Just A
> > MP_perl_global_entries[] = {
> > {"END",MP_GLOBAL_OFFSET(end),MP_GLOBAL_AVCV}, /* END
> */
> >
> > What's global END()? I thought END always belong to some namespace.
>
> nope. PL_endav is global.
Does this mean that any END blocks registered during a request handler,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry for the off topic post, but I'm not sure where else to post...
Has anyone here ever seen "bugs" with requests on an EAPI enabled Apache where
r->per_dir_config is NULL? I haven't managed to replicate the bug yet, but a
number of AxKit users a
On Sun, 2 Jun 2002, Stas Bekman wrote:
> Therefore the following fails:
>
>PerlModule Apache2
>PerlRequire "/home/httpd/httpd-2.0/perl/startup.pl"
>
> if the startup file needs something from Apache2/ (which is in 99% the
> case).
one can always 'use Apache2 ();' in startup.pl instea
On Sun, 2 Jun 2002, Stas Bekman wrote:
> The %ENV part is fine, but why don't I see: EnvTest env var set in the
> config file via subprocess_env? Is it supposed be this way?
see modperl_env.c:
/* XXX: might want to always do this regardless of PerlOptions -SetupEnv */
modperl_env_confi
On Mon, 3 Jun 2002, Stas Bekman wrote:
> The good thing about lib.pm is that it removes duplicates if any.
sure. the bad thing is it is much more expensive and bloated. all the
stats and 'use Config'.
> I've changed the docs to say:
>
> As an alternative to using C in I to adjust
> C<@INC
On Mon, 3 Jun 2002, Stas Bekman wrote:
> I was documenting the env vars set under 2.0, and saw that
> GATEWAY_INTERFACE shouldn't be available under 2.0 unless MP_COMPAT_1X
> is defined. But it's always defined. What's the plan?
it is mainly for documentation at the moment. anything withing
On Mon, 3 Jun 2002, Herbert Rosmanith wrote:
> aha. I had changed that to "use Apache2::APR::Table();" and it worked.
you shouldn't have to do that. do you configure:
PerlModule Apache2
PerlModule Apache::compat
?
> one:
>
> 1)
> return OK unless $r->is_main;
>
> complains that "is_m
On Mon, 3 Jun 2002, Doug MacEachern wrote:
> On Sun, 2 Jun 2002, Stas Bekman wrote:
>
> > The %ENV part is fine, but why don't I see: EnvTest env var set in the
> > config file via subprocess_env? Is it supposed be this way?
>
> see modperl_env.c:
> /* XXX: might want to always do this re
On Mon, 3 Jun 2002, Doug MacEachern wrote:
> On Mon, 3 Jun 2002, Stas Bekman wrote:
>
> > I was documenting the env vars set under 2.0, and saw that
> > GATEWAY_INTERFACE shouldn't be available under 2.0 unless MP_COMPAT_1X
> > is defined. But it's always defined. What's the plan?
>
> it is m
>
> you should retry. even though it isn't the default yet,
> 'PerlModule Apache2' is a noop if modules were installed in the default
> locations. so there is no harm in always having it configured.
>
ok, I will try this, when I get a free time slot, jsut have to mange some
other things before.
On Mon, 3 Jun 2002, Doug MacEachern wrote:
> On Sun, 2 Jun 2002, Stas Bekman wrote:
>
> > Therefore the following fails:
> >
> >PerlModule Apache2
> >PerlRequire "/home/httpd/httpd-2.0/perl/startup.pl"
> >
> > if the startup file needs something from Apache2/ (which is in 99% the
> >
On Mon, 3 Jun 2002, Gerald Richter wrote:
> The otherthing is the test suite, which need to know which version we are
> using and startup.pl need to decide to load Apache::Registry or
> ModPerl::Registry. I currently check $ENV{MOD_PERL}, is there a better way
> to decide, if we are running under
On Mon, 3 Jun 2002, Stas Bekman wrote:
> Does this mean that any END blocks registered during a request handler,
> will be run at the end of it and not at the shutdown? If not where do
> they go if PL_endav is getting reset to its pre-request value.
only if SetHandler is perl-script, PL_endav
On Mon, 3 Jun 2002, Matt Sergeant wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Sorry for the off topic post, but I'm not sure where else to post...
>
> Has anyone here ever seen "bugs" with requests on an EAPI enabled Apache where
> r->per_dir_config is NULL? I haven't managed
On Tue, 4 Jun 2002, Stas Bekman wrote:
> whichever way is fine with me, I was documenting the differences between
> modperl and perl-script and wasn't sure how to document this. So should I
> say:
>
> under the "modperl" handler use Perl{Set,Add}Var instead of
> Perl{Set,Pass}Env. Alternative
On Tue, 4 Jun 2002, Stas Bekman wrote:
> Meaning that we do want to be compatible with 1.x?
yes, wherever possible when it doesn't cause more trouble than it is
worth.
> So Apache::compat is optional but not the configuration directives and a
> few other bits?
Apache::compat is optional beca
On Mon, 3 Jun 2002, Gerald Richter wrote:
> avoid all of the mod_perl 2 conditions in Embperl itself. The only thing
> that is missing at the moment and I think you should add it, is a
>
> require Apache::SubRequest ;
>
> otherwise $r -> lookup_uri etc doesn't work.
this is in compat.pm now.
On Tue, 4 Jun 2002, Stas Bekman wrote:
> Ok, so the advisory should be:
>
> If you use a startup file, add at the top of it:
>
> use Apache2 ();
>
> Only if you don't use a startup file, use:
>
> PerlModule Apache2
>
> or something like this. ok?
sure, but keep in mind if we figure the
On Tue, 4 Jun 2002, Stas Bekman wrote:
> I haven't finished porting the registry family. When I'm done there will
> be no need for Apache::compat to run ModPerl::Registry. Why would you need
> to know whether you are running under Apache::Registry or
> ModPerl::Registry? they are absolutely the
On Tue, 4 Jun 2002, Matt Sergeant wrote:
> Seems to be I think - but then this isn't a bug I've been able to replicate. I
> asked the person to try recompiling with an explicit -DEAPI and it made no
> difference. AxKit uses Apache::src to get the headers and CFLAGS.
>
> Does the request_rec c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 04 June 2002 12:25 am, Doug MacEachern wrote:
> On Tue, 4 Jun 2002, Matt Sergeant wrote:
> > Seems to be I think - but then this isn't a bug I've been able to
> > replicate. I asked the person to try recompiling with an explicit -DEAPI
> >
On Tue, 4 Jun 2002, Matt Sergeant wrote:
> OK, I'm applying the following diff. Does it make sense to you? (I'm
> completely lost as to why I need to do this, so any guidance is most
> welcome!)
looks right to me. same issues that have been plaguing modperl itself
ever since 5.6.0 was relea
On Mon, 3 Jun 2002, Herbert Rosmanith wrote:
> sub trans($$) {
also, this needs to be:
sub trans : method {
which works with both 1.x and 2.x
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMA
On Mon, 3 Jun 2002, Doug MacEachern wrote:
> On Tue, 4 Jun 2002, Stas Bekman wrote:
>
> > Ok, so the advisory should be:
> >
> > If you use a startup file, add at the top of it:
> >
> > use Apache2 ();
> >
> > Only if you don't use a startup file, use:
> >
> > PerlModule Apache2
> >
>
On Mon, 3 Jun 2002, Doug MacEachern wrote:
> On Tue, 4 Jun 2002, Stas Bekman wrote:
>
> > I haven't finished porting the registry family. When I'm done there will
> > be no need for Apache::compat to run ModPerl::Registry. Why would you need
> > to know whether you are running under Apache::Reg
On Mon, 3 Jun 2002, Doug MacEachern wrote:
> On Mon, 3 Jun 2002, Stas Bekman wrote:
>
> > Does this mean that any END blocks registered during a request handler,
> > will be run at the end of it and not at the shutdown? If not where do
> > they go if PL_endav is getting reset to its pre-reque
>
> gerald is talking about configuring the httpd.conf to use one or the other
> for testing. one thing we could do is have modperl add a MODPERL2 define
> internally, as if the server has been started with -DMODPERL2. that can
> be used with in .conf files and with
> if Apache->define("MODPERL
[EMAIL PROTECTED] wrote:
> dougm 2002/06/03 16:41:18
>
> Modified:src/modules/perl mod_perl.c mod_perl.h
> Log:
> add MODPERL2 config define, as if the server had been started with -DMODPERL2
>
> Revision ChangesPath
> 1.121 +10 -2 modperl-2.0/src/modules/perl/
31 matches
Mail list logo
