Are you loading mod_perl.so as a DSO? I understand Apache 1.3.x has
issues with mod_perl as a DSO. I'm not a core developer, but I hope this
helps. I have had no issues running mod_perl statically compiled into
Apache 1.3.x
Your kernel version doesn't raise any alarms for me.
Diona Kidd
Jon
Thanks Tyler,
Unfortunately this wont fix my issue as my apache processes seg fault no
matter what type of file I request, whether its a mod_perl script, an
html file, or just a directory listing, if mod_perl is loaded apache seg
faults constantly. My apache, php, mod_ssl and mod_perl installs
All right!
- Original Message -
From: "Allison Randal" <[EMAIL PROTECTED]>
To: "Stas Bekman" <[EMAIL PROTECTED]>
Cc: "mod_perl List"
Sent: Friday, December 16, 2005 5:42 AM
Subject: Re: Re: Good mp2 books?
> Stas and I are working on an MP2 book, called simply "mod_perl 2.0
> User Gu
Jon Keller <[EMAIL PROTECTED]> wrote:
> I'm trying to build apache 1.3.34 and mod_perl 1.29 on a debian 3.1
> machine and whenever mod_perl is loaded apache segfaults at any type of
> request.
I had a similar problem with Apache2 and mod_perl2. It drove me
absolutely nuts. When I changed
Hello,
I'm trying to build apache 1.3.34 and mod_perl 1.29 on a debian 3.1
machine and whenever mod_perl is loaded apache segfaults at any type of
request.
I've followed the steps at
http://perl.apache.org/docs/1.0/guide/install.html for building mod_perl
both into apache, and as a module.
Philip M. Gollucci wrote:
>> You will only get the Seg fault or Bus error when a process comes round
>> for recycling.
This is basically caused by the assumption that %ENV will be tied, and local
%ENV
breaks that assumption ;-S
The following patch fixes this problem for me:
Index: src/modules/p
Stas and I are working on an MP2 book, called simply "mod_perl 2.0
User Guide". It's based on the current user documentation, but edited
and expanded. If all goes well, it'll be available by the end of
February.
(If you'd like an early preview and have a little time, I'll be
looking for r
On Thu, 2005-12-15 at 01:15 -0600, Chase Venters wrote:
> I could probably get
> some of these answers myself with more study of the mod_perl / perl source,
> but I was hoping someone might just know the answer and be able to tell me :)
Not a great way to start your post. Please read this:
http
From: "Philip M. Gollucci" <[EMAIL PROTECTED]>
I haven't followed this whole thread, so I may be way off base here:
If you're implementing a filter, you're filter handlers _will_ be called as
many times as neccessary.
You can account for multiple invocations or pass along information in
$f->c
Hi,
> Jonathan Vanasco wrote:
> >
> > If you asked Santa to bring you one for Christmas he'd look at you,
> > stare for a moment, and give his jolly ol' laugh just before he says
> > "You're shit out of luck"
> >
> > To the best of my knowledge, there are 3 mod perl 1 (MP1) books :
> > pract
On Thursday 15 December 2005 08:41 am, Enno wrote:
> Looks like you're not pinging your database to verify the db-connection.
> check Apache::DBI manual on how to implement it for Sybase, and how to
> make Apache::DBI ping.
There was a problem with DBD::Sybase's ping call. It was fixed in the las
On Thursday 15 December 2005 04:49 am, Jeremy Kister wrote:
> After my sql server goes off line, Apache::DBI consistently fails, even
> after the sql server comes back online:
> null DBI connect('server=10.0.0.10;database=SCD','user01',...) failed:
> null: DBD::Sybase::st execute failed: OpenClie
Torsten Foertsch wrote:
> Hi,
>
> what is the canonical way to change "Options" from a handler?
I don't think so, as Options is private to httpd
>
> Apache2::Access::allow_options is read-only. Various attempts with
> $r->add_config in the uri translation and header parser phases failed:
>
Looks like you're not pinging your database to verify the db-connection.
check Apache::DBI manual on how to implement it for Sybase, and how to
make Apache::DBI ping.
Enno
On Thu, 15 Dec 2005, Jeremy Kister wrote:
> After my sql server goes off line, Apache::DBI consistently fails, even
> after
After my sql server goes off line, Apache::DBI consistently fails, even
after the sql server comes back online:
null DBI connect('server=10.0.0.10;database=SCD','user01',...) failed:
null: DBD::Sybase::st execute failed: OpenClient message: LAYER = (0)
ORIGIN = (0) SEVERITY = (78) NUMBER = (38)
Hi,
what is the canonical way to change "Options" from a handler?
Apache2::Access::allow_options is read-only. Various attempts with
$r->add_config in the uri translation and header parser phases failed:
$r->add_config([q{Options +ExecCGI}]): $r->add_config() has failed: Options
not allowed he
16 matches
Mail list logo
