Tom Caldwell wrote:
is it possible that this path it not readable by user 'apache'? I doubt
so, since all other tests run just fine.
Well, the LD_LIBRARY_PATH gets set during the bash startup (.bashrc) so
if the test does > su - nobody- then the variable should be set.
so if you dump %ENV from
Jeff Ambrosino wrote:
From within an existing Perl handler/filter, you can dynamically
insert ('register') a new filter with the add_output_filter method on
the request object:
$r->add_output_filter(\&callback);
And, you can remove a downstream filter (from within an upstream filter) with:
$next_f
On tirsdag 03 mai 2005, 00:40, Michael Schout wrote:
> Jeffrey W. Baker wrote:
> > It is possible that the FOR UPDATE is spurious. It signals to the
> > database system that this transaction intends to write that row.
> > With PostgreSQL's MVCC transaction isolation system, it's probably
> > not
[CC'ing the list back]
Caldwell, Thomas S wrote:
I recompiled mod_perl but I did not recompile Apache2, if that is what is
meant by 'everything'.
Hmm, that's a good question. I think you need Apache2 too.
But they are distinct, right, so it shouldn't matter as long as Apache can
incorporate the l
On Mon, 2 May 2005, Joe Schaefer wrote:
> Please test and offer feedback on the second
> release candidate for libapreq2-2.05-dev.
Builds and tests fine on Win32. I've put up a Win32 ppm
package of this (libapreq2) at
http://theoryx5.uwinnipeg.ca/ppms/
which requires the mod_perl ppm package (
On Tue, 2005-05-03 at 11:47 +1000, scott fagg wrote:
> I'm trying to get apache::upload working. Module loads fine, produces no
> errors, but calls to 'upload' don't produce anything usable. For
> example, this snippet of code :
>
> use Apache::Request;
> use Apache::Upload;
> use Data::Dumper;
>
My thanks to the libapreq team for their time and effort on this. Much
appreciated.
Joe Schaefer wrote:
Please test and offer feedback on the second
release candidate for libapreq2-2.05-dev.
The changes since 2.04-dev are too numerous
to list in this email, so please read the
CHANGES file in t
Let me see if I can answer this one.
Your sample code does not use Apache::Request at all. by the way, in the
latest release of modperl RC5, Apache::Request is now renamed to
Apache2::Request. You probably can guess why.
If you wish to use the Apache::Request object, you need to first load
the
I'm trying to get apache::upload working. Module loads fine, produces no
errors, but calls to 'upload' don't produce anything usable. For
example, this snippet of code :
use Apache::Request;
use Apache::Upload;
use Data::Dumper;
$req = Apache::Request->new($r);
$upload = $req->upload();
print D
Jeffrey W. Baker wrote:
> It is possible that the FOR UPDATE is spurious. It signals to the
> database system that this transaction intends to write that row. With
> PostgreSQL's MVCC transaction isolation system, it's probably not
> necessary and may be causing problems.
It definately *is* nec
>From within an existing Perl handler/filter, you can dynamically
insert ('register') a new filter with the add_output_filter method on
the request object:
$r->add_output_filter(\&callback);
And, you can remove a downstream filter (from within an upstream filter) with:
$next_f = $f->next;
$next_
On Mon, 2005-05-02 at 15:08 -0700, Jeffrey W. Baker wrote:
> It is possible that the FOR UPDATE is spurious. It signals to the
> database system that this transaction intends to write that row. With
> PostgreSQL's MVCC transaction isolation system, it's probably not
> necessary and may be causing
Comments below.
On Sat, 2005-04-30 at 01:25, Stas Bekman wrote:
> Tom Caldwell wrote:
> > Stas,
> >
> > I forgot to mention that apache usually runs under a different account
> > than nobody (I use - apache), in case that matters.
>
> Of course. In which case you need to check 'apache' instead o
On Fri, 2005-04-29 at 16:50 +0200, Kjetil Kjernsmo wrote:
> I guess it could be that the use we make of Apache::Session is flawed,
> that we should call an update somewhere, but it works (apparently) with
> the other data stores. It feels like there is something in the
> direction of transactio
Hi ppl,
I have a couple of PerlOutputFilterHandler directives registered in my
httpd.conf conigurations.
Is there any way to activate/deactivate these filters without editing
httpd.conf and restarting Apache?
I'm running Apache 2.0.54 with mod_perl2_RC5.
TIA,
// haver
On Mon, 2 May 2005, Octavian Rasnita wrote:
> Hi,
>
> I have installed libapreq2 under Windows 2000 using ppm because I want to
> use Apache2::Request.
>
> I have tried a simple module:
>
> package Test::Module;
>
> use strict;
> use Apache2::RequestRec ();
> use Apache2::RequestIO ();
> use Apach
hi stas,
although i'm relatively new to its use, /perl-status seems to behave w/
no obvious errors (so far).
if there's any info i can provide that may be helpful, pls let me know.
You need to enable: the terse feature and then follow: Loaded Modules ->
Apache::Const -> Apache::Const::OK -> Syntax
Jeff Ambrosino wrote:
Ok, I tried this approach, and it only partially worked; unfortunately
my httpd procs are still dying, and APR::Error doesn't seem to pass
anything. Here's the error I got _before_ wrapping $f->print in the
eval:
[Sun May 01 05:12:21 2005] [error] [client X.X.X.X]
Apache
OpenMacNews wrote:
hi,
I get the same problem on linux/prefork mpm.
fwiw, i'm seeing no such issues on osx 10.4/worker mpm. no errors, no
suspect log entries, etc.
Embedded Perl version v5.8.6 for Apache/2.1.5-dev process 21420
Server Version: Apache/2.1.5-dev (Unix) DAV/2 SVN/1.2.0-rc2
m
Marc Gràcia wrote:
I had some problems like this on my new x86_64 machine with mod_perl2,
seems that not only perl must be compiled with -fPIC , also apache and
all libraries or modules you plan to use. I think it's a general issue
with this architecture, not mod_perl related.
That's correct, Marc.
jiesheng zhang wrote:
> By this configuration, without the "use Apache::DBI ();" and with
> "$Apache::DBI::DEBUG=1" in the startup.pl, I could not see the debug
> output in the error log.
looks like you hit it on the head. If you don't have
$Apache::DBI::DEBUG=1 in your startup, then you wont see
Hi,
I have installed libapreq2 under Windows 2000 using ppm because I want to
use Apache2::Request.
I have tried a simple module:
package Test::Module;
use strict;
use Apache2::RequestRec ();
use Apache2::RequestIO ();
use Apache2::Const -compile => ':common';
use Apache2::Request ();
sub hand
Perrin Harkins wrote:
On Tue, 2005-05-03 at 00:21 +0800, jiesheng zhang wrote:
I saw debug information in the apache log file after I added the
use Apache::DBI to the startup.pl. However, this is not mentioned in the Apache::DBI documentation. The documentation only mentioned that I should add
On Tue, 2005-05-03 at 00:21 +0800, jiesheng zhang wrote:
> I saw debug information in the apache log file after I added the
>
> use Apache::DBI to the startup.pl. However, this is not mentioned in the
> Apache::DBI documentation. The documentation only mentioned that I should add
> PerlModule Apa
Perrin Harkins wrote:
On Mon, 2005-05-02 at 20:10 +0800, jiesheng zhang wrote:
I indeed set the $Apache::DBI::DEBUG=2 in the
/etc/apache2/mod_perl-startup.pl. However I did not see any debug output
in the apache error log file
Did you "use Apache::DBI" in your startup.pl or httpd.conf?
On Mon, 2005-05-02 at 20:10 +0800, jiesheng zhang wrote:
> I indeed set the $Apache::DBI::DEBUG=2 in the
> /etc/apache2/mod_perl-startup.pl. However I did not see any debug output
> in the apache error log file
Did you "use Apache::DBI" in your startup.pl or httpd.conf?
I think you're not under
Please test and offer feedback on the second
release candidate for libapreq2-2.05-dev.
The changes since 2.04-dev are too numerous
to list in this email, so please read the
CHANGES file in the tarball at
http://people.apache.org/~joes/libapreq2-2.05-dev-rc2.tar.gz
Changes since rc1:
- Win
Ok, I tried this approach, and it only partially worked; unfortunately
my httpd procs are still dying, and APR::Error doesn't seem to pass
anything. Here's the error I got _before_ wrapping $f->print in the
eval:
[Sun May 01 05:12:21 2005] [error] [client X.X.X.X]
Apache::Filter::print: (104
I am using the SuSE 9.1 which has apache 2.0 and mod_perl 1.99_12.
I did not see any Apache::DBI debug information in the apache error log.
jiesheng, please read the module's manpage:
http://search.cpan.org/dist/Apache-DBI/DBI.pm
To enable debugging the variable $Apache::DBI::DEBUG must be set
Why not just do that in your modperl startup script?
use lib '/usr/local/myproject/...';
Enno
On Mon, 2 May 2005, Jan Poslusny wrote:
> Hi modperl gentlemen,
> I am newbie in this list, but I have some experience with mod_perl. I
> use apache 1.3 with statically linked mod_perl 1.29 on Fedora C
Hi modperl gentlemen,
I am newbie in this list, but I have some experience with mod_perl. I
use apache 1.3 with statically linked mod_perl 1.29 on Fedora Core III,
i386. Now I started development of Apache::MyModule from scratch. I
don't want to install MyModule.pm into standard perl directories
hi,
I get the same problem on linux/prefork mpm.
fwiw, i'm seeing no such issues on osx 10.4/worker mpm. no errors, no suspect
log entries, etc.
Embedded Perl version v5.8.6 for Apache/2.1.5-dev process 21420
Server Version: Apache/2.1.5-dev (Unix) DAV/2 SVN/1.2.0-rc2
mod_perl/1.999.23-dev
I had some problems like this on my new x86_64 machine with mod_perl2, seems that not only perl must be compiled with -fPIC , also apache and all libraries or modules you plan to use. I think it's a general issue with this architecture, not mod_perl related.
If not, there are runtime linking re
Octavian Rasnita wrote:
Hello,
I have finished (I hope) installing mod_perl rc5 under Windows 2000, and I
have tried the server using http://localhost/perl-status.
I was able to use it very well, until I have tried to see the following
links in order:
Loaded Modules - Apache::Const - Apache::Const:
34 matches
Mail list logo
