> > I tried setting Lock to File instead of Null, but there is some sort
> > of contention issue because after the first request all other requests
> > hang like they are waiting for a lock to be release.
>
> This usually means you have a scoping bug in your code. If the session
> object never go
Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
> --
> Meanwhile I've found a solution proposed by Andreas 1.5 years ago, which
> might work as a better workaround from all the ones proposed so far:
> http://www.xray.mpe.mpg.de/mailin
Hi,
I want to configure a production server that uses mod_perl and I don't know
what version to choose because I see that mod_perl 2 is not stable yet.
What do you recommend, to install Apache 1.3 and mod_perl 1 and use it until
mod_perl 2 will be stable enough, or do you think that mod_perl 2 can
>
> > I tried setting Lock to File instead of Null, but there is some sort
> > of contention issue because after the first request all other requests
> > hang like they are waiting for a lock to be release.
>
> This usually means you have a scoping bug in your code. If the session
> object never
On Thu, Dec 30, 2004 at 07:32:19PM -0500, Stas Bekman wrote:
> >Hmm, that's what I thought too and was creating a symlink from
> >/usr/lib/libperl.so to the newly created one. I was still getting
> >strange behavior though so moved them all out of /usr/lib. Seems a bit
> >better now.
>
> If the ap
I've summarized the discussions that have happened on modperl users and
dev, and p5p lists. I think I've addressed all the raised questions and
tried to provide extensive answers:
http://perl.apache.org/docs/2.0/user/porting/porting.html#The_Conflict_of_mp1_vs_mp2_vs_mp22_vs_vs_mpNN
If I've
Hess, Fraser wrote:
Here is the log. 9599 is the transaction when I first call the web page
in the browser. 9600 is when I try on log on when the realm is blank.
9601 is from when I successfully authenicate, using basic it seems.
[9600] AuthenNTLM: protocol=NTLMSSP, type=3, [EMAIL PROTEC
William McKee wrote:
On Thu, Dec 30, 2004 at 07:00:36PM -0500, Stas Bekman wrote:
I'm guessing that this goes for any libperl.so, e.g. libperl.so.5.6 or
libperl.so.5.8. If so then it would explain the weird behavior that I've
been getting when compiling mod_perl.
Normally in addition to libperl.so.
On Thu, Dec 30, 2004 at 07:00:36PM -0500, Stas Bekman wrote:
> >I'm guessing that this goes for any libperl.so, e.g. libperl.so.5.6 or
> >libperl.so.5.8. If so then it would explain the weird behavior that I've
> >been getting when compiling mod_perl.
>
> Normally in addition to libperl.so.5.8 the
William McKee wrote:
On Thu, Dec 30, 2004 at 05:57:07PM -0500, Stas Bekman wrote:
As [2] explains you have more than one libperl.so and the wrong one gets
loaded. libperl.so should *not* be in /usr/lib or any other globally seen
loader path if you want to have more than one perl on the same syste
On Thu, Dec 30, 2004 at 05:57:07PM -0500, Stas Bekman wrote:
> As [2] explains you have more than one libperl.so and the wrong one gets
> loaded. libperl.so should *not* be in /usr/lib or any other globally seen
> loader path if you want to have more than one perl on the same system.
> Unfortuna
Torsten Foertsch wrote:
On Friday 29 October 2004 22:13, Stas Bekman wrote:
Torsten Förtsch wrote:
On Friday 29 October 2004 20:17, Stas Bekman wrote:
perl allows to modify $0. Then top, ps & co would display the new
process title. Can the process title of a mod_perl modified apache be
set this way
William McKee wrote:
Hi folks,
I'm trying to recompile Perl and Apache/mod_perl on a Debian Sarge
system using the following versions:
Perl 5.8.6
Apache 1.3.33
mod_perl 1.29
I am compiling mod_perl statically (using Apachetoolbox) with the
following options:
APACHE_PREFIX=/usr/local/apache
My bad :(...
All tests run fine now.
Sorry,
Patrick
- Original Message -
> Patrick LeBoutillier wrote:
>> Stas,
>>
>> Maybe you read a bit too quickly... :)
>>
>>
I saw someone having similar errors with Apache 2.1.x, but I'm running
>>
>> 2.0.52.
>
> Doh, my apologies: ETOOMANYEMA
Chris Ochs said:
> I have found three things that need to be worked around like this in
> order to use this approach. One is frames like you said, the other is
> not pulling in stylesheets via an href, and the other is making sure
> images are not loaded through mod perl. If I do all of that I d
> So you have a lost update problem. There is probably a way to structure
> things to avoid this (maybe not using sessions for it), but some form of
> mutually exclusive locking would fix it, at the expense of making your
> site slower, since each frame will have to wait for its turn. You might
>
Hi folks,
I'm trying to recompile Perl and Apache/mod_perl on a Debian Sarge
system using the following versions:
Perl 5.8.6
Apache 1.3.33
mod_perl 1.29
I am compiling mod_perl statically (using Apachetoolbox) with the
following options:
APACHE_PREFIX=/usr/local/apache
APACHE_SRC=/us
Patrick LeBoutillier wrote:
Stas,
Maybe you read a bit too quickly... :)
I saw someone having similar errors with Apache 2.1.x, but I'm running
2.0.52.
Doh, my apologies: ETOOMANYEMAILS
Please submit a proper bug report:
http://perl.apache.org/bugs/
in particular:
http://perl.apache.org/docs/2.0/u
Stas,
Maybe you read a bit too quickly... :)
>> I saw someone having similar errors with Apache 2.1.x, but I'm running
2.0.52.
All my setup is all stock Fedora Core 3 rpm's and up-to-date:
perl-5.8.5-9
httpd-2.0.52-3.1
httpd-devel-2.0.52-3.1
apr-0.9.4-23
apr-devel-0.9.4-23
Cheers,
Patrick
Chris Ochs said:
> The issue I am having is that the postgresql store doesn't do any
> locking
It should. It uses "SELECT FOR UPDATE" which grabs an exclusive lock on
the row in question until a commit is issued. A::S doesn't issue the
commit, so you have to do that yourself. Have you been mess
Patrick LeBoutillier wrote:
Hi all,
I get the following test errors on a plain Fedora Core 3 install:
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t/api/access2.t
Hi all,
I get the following test errors on a plain Fedora Core 3 install:
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t/api/access2.t 63 50.00% 2 5-6
Michael Heidel wrote:
Hi List,
we got a strange problem on Apache/2.0.52 (Unix) mod_perl/1.99_18
Perl/v5.8.5.
$r->content_type('image/jpeg');
$r->sendfile($docname);
returns an empty image (length: 0).
it doesn't return anyhing but success code
The jpg image $docname exists and is readable for ap
On Friday 29 October 2004 22:13, Stas Bekman wrote:
> Torsten Förtsch wrote:
> > On Friday 29 October 2004 20:17, Stas Bekman wrote:
> >>>perl allows to modify $0. Then top, ps & co would display the new
> >>> process title. Can the process title of a mod_perl modified apache be
> >>> set this way?
Hi List,
we got a strange problem on Apache/2.0.52 (Unix) mod_perl/1.99_18
Perl/v5.8.5.
$r->content_type('image/jpeg');
$r->sendfile($docname);
returns an empty image (length: 0).
The jpg image $docname exists and is readable for apache.
Also error handling does not work:
If we change $document t
On Thu, 30 Dec 2004 10:00:32 +0200, Octavian Rasnita <[EMAIL PROTECTED]> wrote:
> If this happens only in pages with frames, try creating a page without
> frames.
Umm no, I want a solution not a work around. This application is used
by a lot of people on a lot of different sites with the file bac
26 matches
Mail list logo
