Joshua Hoblitt wrote:
On Tue, 21 Dec 2004, Stas Bekman wrote:
Joshua Hoblitt wrote:
[This thread really belongs to the httpd-test list, since it has
nothing to do with modperl]
[...]
"Apache/1.3.33 (Unix) mod_perl/1.29" and I'm using
Apache::Test/Apache::TestMB 1.17.
what code do you have in yo
On Tue, 21 Dec 2004, Stas Bekman wrote:
Joshua Hoblitt wrote:
[This thread really belongs to the httpd-test list, since it has nothing to
do with modperl]
[...]
"Apache/1.3.33 (Unix) mod_perl/1.29" and I'm using
Apache::Test/Apache::TestMB 1.17.
what code do you have in your tests that invokes
Randy Kobes wrote:
On Tue, 21 Dec 2004, Geoffrey Young wrote:
-verbose=0 APXS (/usr/local/apache/bin/apxs) query for SBINDIR failed
APXS (/usr/local/apache/bin/apxs) query for TARGET failed APXS
(/usr/local/apache/bin/apxs) query for SYSCONFDIR failed APXS
(/usr/local/apache/bin/apxs) query for PR
On Tue, 21 Dec 2004, Geoffrey Young wrote:
> > -verbose=0 APXS (/usr/local/apache/bin/apxs) query for SBINDIR failed
> > APXS (/usr/local/apache/bin/apxs) query for TARGET failed APXS
> > (/usr/local/apache/bin/apxs) query for SYSCONFDIR failed APXS
> > (/usr/local/apache/bin/apxs) query for PREFI
> $ make test /usr/bin/perl5.8.5 Build --makefile_env_macros 1 test
> /usr/bin/perl5.8.5 -I
> /home/moa/jhoblitt/docs/perl/dev/modules/PS-IPP-IData/blib/lib -I
> /home/moa/jhoblitt/docs/perl/dev/modules/PS-IPP-IData/blib/arch t/TEST
> -clean [warning] setting ulimit to allow core files ulimit
Configured with:
perl Makefile.PL MP_INST_APACHE2=1 MP_AP_PREFIX=/usr/local/apache-2.0.52/
make && make install
OK. Why do you use MP_AP_PREFIX and not MP_APXS? The docs suggest to use
the latter:
http://perl.apache.org/docs/2.0/user/intro/start_fast.html#Installation
http://perl.apache.org/docs
Joshua Hoblitt wrote:
[This thread really belongs to the httpd-test list, since it has nothing
to do with modperl]
[...]
"Apache/1.3.33 (Unix) mod_perl/1.29" and I'm using
Apache::Test/Apache::TestMB 1.17.
what code do you have in your tests that invokes those?
Any of the .t files that have "u
On Mon, 20 Dec 2004, Stas Bekman wrote:
Joshua Hoblitt wrote:
Hi Folks,
I've been unable to figure out how to get Apache::TestMB to setup my
build
environment in such a way as to suppress APXS warnings during a test run.
e.g.
--
t/10_client_newAPXS (/usr/local/apache/bin/
Thanks for the quick reply.
I cleaned up my installation and reinstalled.
See attached bug report and BuildConfig.pm.
Configured with:
perl Makefile.PL MP_INST_APACHE2=1 MP_AP_PREFIX=/usr/local/apache-2.0.52/
make && make install
The leak persist after reinstall.
I do not have a sample scri
"eps com estem" <[EMAIL PROTECTED]> writes:
[...]
> One last question, would you use libapreq2 to handle all GET
> and POST data or only the multipart-POST data??
It's designed to be usable for all GET / POST data.
The Content-Types it currently understands are
application/x-www-form-urle
Jean-François Nadeau wrote:
Hi all,
I was using mod_perl-1.99_14 under Apache 2.0.49,
I upgraded to mod_perl-2.0.0-RC1 under Apache 2.0.52.
Im using RedHat 8.0 / perl 5.8.0 / CGI.pm 3.05
Apache configuration :
SetHandler perl-script
PerlResponseHandler ModPerl::PerlRun
PerlOptions +Par
Does this have something to do with SElinux?
At what security level is your SE-Linux turn on?
Because on FC2 SE was by default set to high.
Jay Scherrer
On Tuesday 21 December 2004 02:44 am, Chetan Anand wrote:
> Hi,
> Whenever I execute a Perl script the following error
> is displayed in apache
Joel wrote:
Good morning,
This is not a problem, per se, nor is it something I especially need to
get done, but it would certainly be nice to have and might, in some small
way, benefit the world in general. Here's what's going on:
I am using mod_perl 1.99_13 (yes, I know I should upgrade) and Apach
On Tue, 21 Dec 2004, eps com estem wrote:
> >> Here's a patch for $upload->slurp, see if it helps:
> >Fast work, as always, Joe :) These patches I've incorporated
> >in a new libapreq2.ppd ppm package at
> >> href="/app/message?l=es&o=8&url=http%3A%2F%2Ftheoryx5%2Euwinnipeg%2Eca%2Fppms%2F"
> t
The problem might be
in RegistryCooker.pm
I upgraded each
script from 1.99_14 to current one by one to find the leak starts when
using the current RegistryCooker.pm
Let me know if this help...
thanks
From: Jean-François Nadeau
[mailto:[EMAIL PROTECTED] Sent: 21 décembre 2004
08:15T
Good morning,
This is not a problem, per se, nor is it something I especially need to
get done, but it would certainly be nice to have and might, in some small
way, benefit the world in general. Here's what's going on:
I am using mod_perl 1.99_13 (yes, I know I should upgrade) and Apache
2.0.52.
Although I doubt this has something todo with mod_perl which this list
is dedicated to you should at least state:
* Version of DBI.pm
* Maybe also the part of DBI.pm around line 514
* try to run a programm on the command-line using DBI if it also fails
=> upgrade DBI.pm (are the version on the
Hi
all,
I was using
mod_perl-1.99_14 under Apache 2.0.49,
I upgraded to
mod_perl-2.0.0-RC1 under Apache 2.0.52.
Im using RedHat 8.0
/ perl 5.8.0 / CGI.pm 3.05
Apache configuration
:
SetHandler
perl-script PerlResponseHandler ModPerl::PerlRun PerlOptions
+ParseHeaders +GlobalReq
I guess the problem might be with your PerlHandler, coz Apache::Registry,
caches all scripts, as a result certain global values will remain
persistent. In such a case you might want to use Apache::PerlRun instead ,
which mimics mod_cgi by flushing the namespace at the every start of
request.
Th
Please provide information about the versions of mod_perl and apache
that you are using. If you provide your fully working configuration
file, it will be easy to identify the issue.
- Pratik
--
http://pratik.syslock.org
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://per
Hello,
I've got a mod_perl-Apache running, which hosts multiple
developement-versions (of multiple CVS-developers) of a webapp.
Therefore I've got this apache-config:
Options +Includes
XBitHack on
SetHandler perl-script
PerlHandler Apache::Registry
PerlModule Apache::DBI
> Оригинално писмо
>От: Stas Bekman <[EMAIL PROTECTED]>
>Относно: Re: What's wrong with this system's configuration?
>До: Nick *** <[EMAIL PROTECTED]>
>Изпратено на: Петък, 2004, Декември 17 18:18:34 EET
>--
>
>Nick *** wrote:
>
>> >>
Hi,
Whenever I execute a Perl script the following erroris displayed in apache's error_log:[error] [client 127.0.0.1] Can't use string ("") as aHASH ref while "strict refs" in use at/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi/DBI.pmline 514., referer: http://localhost/myforms/login.pl
>> Here's a patch for $upload->slurp, see if it helps:
>Fast work, as always, Joe :) These patches I've incorporated
>in a new libapreq2.ppd ppm package at
>href="/app/message?l=es&o=8&url=http%3A%2F%2Ftheoryx5%2Euwinnipeg%2Eca%2Fppms%2F"
target="_blank">http://theoryx5.uwinnipeg.ca/ppms/
>The
24 matches
Mail list logo
