Hey everyone.
I am working on updating Apache::AuthCookie to work with mod_perl
2.0.0-RC5. In past releases, both the MP1 and MP2 versions of
AuthCookie were installed as Apache::AuthCookie, even though the MP2
version of the module has several API changes in order to be compatible
with MP2.
On Fri, 2005-04-15 at 23:46 +0200, Rick Jansen wrote:
> No, that should not be the case, I think. The env-open and the "new
> BerkeleyDB::Hash" are actually called in the run routine, like below,
> simplified.
What you have below will call run() during startup. All the code
outside of subs in yo
Perrin Harkins zee op 15/4/05 17:19:
> Rick Jansen wrote:
>> # crashes:
>> my $DB_Object = new BerkeleyDB::Hash
>> -Filename => $DB,
>>-Env => $Env,
>> -Flags => DB_RDONLY ...
>
> The rest of the flags here may be relevant.
Gokul P. Nair wrote:
A simple call to set_login_cookie.html from a browser
causes a segmentation fault and generates the
following message in my apache error log:
[notice] child pid x exit signal Segmentation
fault (11)
Could you provided a gdb strack trace ?
A simple call to set_login_cookie.html from a browser
causes a segmentation fault and generates the
following message in my apache error log:
[notice] child pid x exit signal Segmentation
fault (11)
set_login_cookie.html:
hello
<%init>
my $cookie = Apache::Cookie->new
( $r,
-n
On Fri, 2005-04-15 at 17:58 +0100, angie ahl wrote:
> So if you had a free choice of OS and control panel what would you go
> with and why.
I'd go with whatever the person who is supposed to admin the box knows
best.
- Perrin
On Fri, 2005-04-15 at 18:39 +0100, Graham Vickrage wrote:
> It shows previously viewed pages and with no particular pattern. Does
> anyone know where I start looking to solve this one.
How about showing us some code? Try to reduce it to a minimal piece
that demonstrates the problem.
Chances are
Philippe, please take a look at this report. It's the same problem you
have been working on 1.5 years ago, but which was never resolved. Here is
the relevant thread:
http://www.gossamer-threads.com/lists/modperl/dev/7190#7190
Thanks.
In case you don't have the original report by Eduard, here it
I'm getting a new server and was planning on going with Fedora Core 3
and plesk. But it was just suggested that I maybe consider FreeBSD and
DA. Never even heard of DA (about to look it up) but being a Mac user
I must know a little about FreeBSD.
I'm going to have to chime in after all my FreeBSD p
Output of "make test"
=
t/TEST -bugreport -verbose=0
[warning] setting ulimit to allow core files
ulimit -c unlimited; /usr/bin/perl5.8.6 /tmp/mod_perl-2.0.0-RC5/t/TEST
-bugreport -verbose=0
[ info] consider removing an old /tmp/mod_perl-2.0.0-RC5/core file
before running te
On Apr 15, 2005, at 1:43 PM, Dan Brian wrote:
FreeBSD is fast, clean, and well-supported. Best server OS I've used.
We're in the process of moving all of our web stuff to FreeBSD as well.
Sometimes something similar happens to me when I'm working on my dev
machine and have automatic reloading turned on via Apache::Reload
Many times, Apache::Reload doesn't pick up the file change, or, for
whatever reason, gets really screwed up and needs a reboot
doing a /usr/local/apache2/bin/a
I'm getting a new server and was planning on going with Fedora Core 3
and plesk. But it was just suggested that I maybe consider FreeBSD and
DA. Never even heard of DA (about to look it up) but being a Mac user
I must know a little about FreeBSD.
So if you had a free choice of OS and control panel
I'm a newbie to Mod perl and have a odd problem.
I have installed apache2 2.0.53, perl 5.8.4 and MP2 2.0.0 and connect to
a postgresql database on a different machine (Apache:DBI & DBI &
DBD::Pg). All works well except that I seem to get old pages served on
new page requests. It would appear as if
Eduard Rozenberg wrote:
[...]
server has died with status 255 (please examine t/logs/error_log)
[ error] oh jeez, server dumped core
[ error] for stacktrace, run: gdb /usr/sbin/httpd -core
/tmp/mod_perl-2.0.0-RC5/core
Eduard, please read again the bug reporting guidelines. You need to submit
a
FC3 of course, FC2 has been retired.
Jay Scherrer
On Fri, 2005-04-15 at 17:08 +0100, angie ahl wrote:
> Hi guys
>
> I'm getting a new server set up with rackcheck and I've chosen fedora
> core, as I sort of know it.
>
> It's also going to have plesk on it which I've not used at all yet,
> but l
> I'm getting a new server and was planning on going with Fedora Core 3
> and plesk. But it was just suggested that I maybe consider FreeBSD and
> DA. Never even heard of DA (about to look it up) but being a Mac user
> I must know a little about FreeBSD.
>
> So if you had a free choice of OS and c
angie ahl wrote:
Hi guys
Hello,
I'm getting a new server and was planning on going with Fedora Core 3
and plesk. But it was just suggested that I maybe consider FreeBSD and
DA. Never even heard of DA (about to look it up) but being a Mac user
I must know a little about FreeBSD.
OSX mmm yum ;p neve
Hi guys
I'm getting a new server and was planning on going with Fedora Core 3
and plesk. But it was just suggested that I maybe consider FreeBSD and
DA. Never even heard of DA (about to look it up) but being a Mac user
I must know a little about FreeBSD.
So if you had a free choice of OS and cont
angie ahl wrote:
Hi guys
I'm getting a new server set up with rackcheck and I've chosen fedora
core, as I sort of know it.
It's also going to have plesk on it which I've not used at all yet,
but looks better than Ensim
They've asked which version of Fedora I want. Fedora Core 2 or 3.
Any suggestion
Hi guys
I'm getting a new server set up with rackcheck and I've chosen fedora
core, as I sort of know it.
It's also going to have plesk on it which I've not used at all yet,
but looks better than Ensim
They've asked which version of Fedora I want. Fedora Core 2 or 3.
Any suggestions/warnings. I
Rick Jansen wrote:
# crashes:
my $DB_Object = new BerkeleyDB::Hash
-Filename => $DB,
-Env => $Env,
-Flags => DB_RDONLY ...
The rest of the flags here may be relevant.
To avoid name collisions the application is split in a ma
Tom Schindl wrote:
> It's not really a problem only the error-message is missleading. Take
> the following scenario:
>
> * mp-1.29 installed
> * mp-1.99_21 installed
>
> Run perl Makefile.PL and you'll get a completely missleading error-message:
right - the reason is sound (bad mp2 found) but
Tom Schindl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The reason to flip the lines is simply that you if you require mod_perl
before you modify the @INC using Apache2 the wrong mod_perl (the one of
mp1 is found). But that should be obvious, not?
Appologies, your logic seems sound. Thats
I did an analysis of the performance of different caching modules a little
while back which I posted to this list. At the time one of the caches I
benchmarked was Cache::FileCache. I just received an email from someone
pointing out that it's worth knowing that Cache::SizeAwareFileCache is many,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The reason to flip the lines is simply that you if you require mod_perl
before you modify the @INC using Apache2 the wrong mod_perl (the one of
mp1 is found). But that should be obvious, not?
Tom
Tom Schindl schrieb:
| and here against current svn-trunk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
and here against current svn-trunk.
Tom
Tom Schindl schrieb:
| The patch I submitted was against the Makefile.PL included into the
| distro rc5 and there it read the following:
|
| 8<
| my $old_mp2 = eval { requir
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The patch I submitted was against the Makefile.PL included into the
distro rc5 and there it read the following:
- 8<
my $old_mp2 = eval { require Apache2 };
require mod_perl;
if( ) {
}
-
I'm converting an existing CGI-script that uses Berkely DB with CDB to a
mod_perl version, and I'm running into a problem. The first run works
fine, but the second hit causes a "child pid ... exit signal
Segmentation fault (11)" in the following line, UNLESS I close the
environment after each run,
Philip M. Gollucci wrote:
I'll try to duplicate this soonish error locally soonish.
I just downloaded mp21.29 and apache1.3.33
cd mod_perl-1.29
perl Makefile.PL EVERYTHING=1
answer y both questions
make install
next the mp2 and httpd2 part
cd mod_perl2
perl Makefile.PL \
MP_APXS=/home/pgoll
Tom Schindl wrote:
Index: Makefile.PL
===
--- Makefile.PL (revision 161423)
+++ Makefile.PL (working copy)
@@ -14,8 +14,8 @@
BEGIN {
eval {
require mod_perl;
+if ($mod_perl::VERSION < 1.999_22 && $old_mp2) {
Tom Schindl wrote:
Why doesn't it install if mp1 is installed? Now that we have a new
namespace that should not be a problem?
>incompatible with all prior mod_perl 1.99 releases to date. in
I'm hoping you read that wrong as 1.99 is actually mp2.
Please forgive me if I didn't give you enough cr
Tom Schindl wrote:
I know that I could use the multi-env-unstable in
_MUST_
http://svn.apache.org/repos/asf/httpd/apreq/branches/multi-env-unstable.
With the new rc5 but is there a release planed anytime soon. To reflect
the changes on the mod-perl2-side?
Hi,
Please subscribe to [EMAIL PROTECTED]
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I know that I could use the multi-env-unstable in
http://svn.apache.org/repos/asf/httpd/apreq/branches/multi-env-unstable.
With the new rc5 but is there a release planed anytime soon. To reflect
the changes on the mod-perl2-side?
Tom
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It's not really a problem only the error-message is missleading. Take
the following scenario:
* mp-1.29 installed
* mp-1.99_21 installed
Run perl Makefile.PL and you'll get a completely missleading error-message:
- 8<
35 matches
Mail list logo
