Perrin Harkins wrote:
On Tue, 2004-05-18 at 10:41, Tom Williams wrote:
Thanks for the info. I'm responding off the list since my mod_perl
questions have basically been answered.
You really should keep these questions on the list. Others on there are
much more knowledgeable than I am abou
Tom Williams wrote:
I do notice that from time to time the multi-threaded child
processes will die off and new ones spawn and I understand this is
normal for the Apache 2.0 work MPM. So, each time a child process
terminates the Perl interpreter for that process goes with it and the
new child g
Perrin Harkins wrote:
Tom Williams wrote:
" If sometimes flags are here, problem is in loading the domains.pm
(making country array not loaded correctly) file.
Because yo use mod_perl and i known this module has a very special
way to load pm files and to initialize perl variables (variables are
Tom Williams wrote:
" If sometimes flags are here, problem is in loading the domains.pm
(making country array not loaded correctly) file.
Because yo use mod_perl and i known this module has a very special way
to load pm files and to initialize perl variables (variables are kept in
memory between
Hi! I'm trying to get some help in figuring out why I'm having problems
with some AWStats perl modules in my Apache 2.0.48 (worker
MPM)/mod_perl-1.99_13/Perl 5.8.2 (multi-threaded) on Redhat 9 Linux
environment.
Here is a link to the AWStats weblog analyzer:
http://awstats.sourc
Erik Scholtz, ArgonSoft GmbH wrote:
I think, the problem has to do with mod_perl, because when I run the
script on the console, everything works fine. If I run the script
without mod_perl (over the web with apache), the script also works
without any problems. The script also works with mod_perl
It isn't so much mod_perl as it is the perl DBI::mysql driver...
I imagine that as 4.1.1 comes out of alpha eventually the
maintainers will update to the new libraries...
You might also want to be aware that if you added users while
mysql was in 'new passwords' mode, they'll have the long pass
Garrison Hoffman wrote:
On Tue, 2004-05-11 at 05:02, Erik Scholtz, ArgonSoft GmbH wrote:
failed: Client does not support authentication protocol requested by
server; consider upgrading MySQL client at
This may help:
http://dev.mysql.com/doc/mysql/en/Old_client.html
Thanks for your answer. Th
On Tue, 2004-05-11 at 05:02, Erik Scholtz, ArgonSoft GmbH wrote:
> failed: Client does not support authentication protocol requested by
> server; consider upgrading MySQL client at
This may help:
http://dev.mysql.com/doc/mysql/en/Old_client.html
--
On Tue, 2004-05-11 at 05:02, Erik Scholtz, ArgonSoft GmbH wrote:
> failed: Client does not support authentication protocol requested by
> server; consider upgrading MySQL client at
This may help:
http://dev.mysql.com/doc/mysql/en/Old_client.html
--
, there is no problem, on the other the
problem drives me mad.
My configuration:
-
System with problem:
FreeBSD 5.1-RELEASE #3
Apache/2.0.49
mod_perl/1.99_13
Perl/v5.8.0
mysql-4.1.1 Client
DBD::mysql 2.9003
System without problem:
Hi again,
just for "completeness":
MP 1.99_13/Perl 5.9.1/Apache 2.48/Linux 2.4.22 -
"make test" gave "All tests successful"
(without "::1 localhost ipv6-localhost ipv6-loopback" in
/etc/hosts)
Helmut
>>
>>
>> and test, whether i can connect to one of the listen-ports (e.g.
In a stolen moment ... :-)
-8<-- Start Bug Report 8<--
1. Problem Description:
The following tests failed:
pr-ext/uuid...1..3
Can't load
'/export/home/rob/distros/mod_perl-1.99_13/blib/arch/auto/APR/APR.so'
for module APR
er there."
>
> I have tried the following iterations, all producing the exact same "make
> test" failures:
>
> perl 5.8.3 downloaded from cpan (also tried 5.8.3 from sunfreeware.com)
> mod_perl 1.99_12, mod_perl 1.99_13, and mod_perl 2.0 (latest dev release)
> all
[cc'ing Toby who is in the same boat]
Kinyon, Rob wrote:
t/filter/both_str_con_add.t43 75.00% 2-4
t/protocol/echo.t 22 5632 32 66.67% 2-3
t/protocol/echo_filter.t 22 5632 32 66.67% 2-3
Interesting, all 3 test have one thing in common -
Stas Bekman wrote:
Kinyon, Rob wrote:
Rob, please submit a properl bug report: http://perl.apache.org/bugs/
You can't be bothered to help us resolve your problems? :(
__
Stas BekmanJAm_pH --> Just Another mod_perl Hac
> t/filter/both_str_con_add.t43 75.00% 2-4
> t/protocol/echo.t 22 5632 32 66.67% 2-3
> t/protocol/echo_filter.t 22 5632 32 66.67% 2-3
Interesting, all 3 test have one thing in common - they use a raw socket
to
communicate with the clien
Helmut Zeilinger wrote:
--On Thursday, March 25, 2004 11:45:54 -0800 Stas Bekman <[EMAIL PROTECTED]>
wrote:
and test, whether i can connect to one of the listen-ports (e.g.
"netcat localhost 8529 -vv") => conection refused
so:
netcat localhost 8529 -vv
doesn't work. but:
netcat 127.0.0.1 85
--On Thursday, March 25, 2004 11:45:54 -0800 Stas Bekman <[EMAIL PROTECTED]>
wrote:
>
and test, whether i can connect to one of the listen-ports (e.g.
"netcat localhost 8529 -vv") => conection refused
>
> so:
>
>netcat localhost 8529 -vv
>
> doesn't work. but:
>
>netcat 12
Kinyon, Rob wrote:
Rob, please submit a properl bug report: http://perl.apache.org/bugs/
2) _13 compiled fine using 2.0.49. However, it will not pass the tests.
I removed all mention of RewriteEngine, but still ran into problems. The
error log has no errors in it. The only item is that it seems t
Geoffrey Young wrote:
+
+RewriteEngine On
actually, rewrite seems to be a leftover, maybe from when the test was being
originally written - I can't see the need for rewrite at all and removing
the RewriteEngine directive still allows the tests to pass (as you mentioned).
bu
and test, whether i can connect to one of the listen-ports (e.g. "netcat
localhost 8529 -vv") => conection refused
so:
netcat localhost 8529 -vv
doesn't work. but:
netcat 127.0.0.1 8529 -vv
right?
I replaced all "localhost:" directives in http.conf by
127.0.0.1: =>
at least i get a conne
> +
> +RewriteEngine On
actually, rewrite seems to be a leftover, maybe from when the test was being
originally written - I can't see the need for rewrite at all and removing
the RewriteEngine directive still allows the tests to pass (as you mentioned).
but let's let stas l
Geoffrey Young wrote:
>>I'm having problems in that some of the tests in _12 and _13 use
>>RewriteEngine, which I have disabled. To get _12 to pass, I had to
>>delete all mention of "RewriteEngine".
>
>
> please try the attached patch.
oops, sorry - I forgot to change one thing. please discar
> I'm having problems in that some of the tests in _12 and _13 use
> RewriteEngine, which I have disabled. To get _12 to pass, I had to
> delete all mention of "RewriteEngine".
please try the attached patch.
--Geoff
Index: t/filter/both_str_req_proxy.t
===
listening (TestDirective::perlloadmodule4)
server localhost:8547 listening (TestDirective::perlloadmodule5)
server localhost:8548 listening (TestDirective::perlloadmodule3)
server localhost:8549 listening (TestDirective::perlloadmodule6)
t/apr-ext/uuid...1..3
Can't load
'/export/home/rob
>>>> i tested MP 1.99_13 with Perl 5.8.3 and got the same result - none
>>>> of the tests succeeded / no access to httpd (still empty
>>>> t/logs/access_log).
>>>
>>> OK, let's try the debug-by-proxy technique ;)
>>>
>>
Dr. Helmut Zeilinger wrote:
i tested MP 1.99_13 with Perl 5.8.3 and got the same result - none
of the tests succeeded / no access to httpd (still empty
t/logs/access_log).
OK, let's try the debug-by-proxy technique ;)
once you have build mod_perl 1.99_13 and ready to run 'make test&#
>>
>> i tested MP 1.99_13 with Perl 5.8.3 and got the same result - none
>> of the tests succeeded / no access to httpd (still empty
>> t/logs/access_log).
>
> OK, let's try the debug-by-proxy technique ;)
>
> once you have build mod_perl 1.99_13
Helmut Zeilinger wrote:
Hi,
i tested MP 1.99_13 with Perl 5.8.3 and got the same result - none
of the tests succeeded / no access to httpd (still empty t/logs/access_log).
OK, let's try the debug-by-proxy technique ;)
once you have build mod_perl 1.99_13 and ready to run 'make test&#
Hi,
i tested MP 1.99_13 with Perl 5.8.3 and got the same result - none
of the tests succeeded / no access to httpd (still empty t/logs/access_log).
I also tried the cvs version - same result.
I recompiled and testet MP 1.99_12 again
(to go shure, that nothing else has made the tests fail) -
all
Helmut Zeilinger wrote:
on Linux 2.4.22/Apache 2.48/Perl 5.9.0 the compilation of mp 1.99_13
failed (see below).
Is it because of Perl version 5.9.0? Must i downgrade to Perl 5.8.x
again?
It's because you have an old 5.9.0. Only the very latest blead perl is
supported. Upgrade to the current blead
ou said, you are running 5.9.1. How come your report is from
> 5.9.0. Did you rebuild mod_perl with the right perl? Also your mod_perl
> version is 1.99_12 where supposedly you are talking about 1.9_13.
>
No, it's really mp 1.99_13 and Perl 5.9.1. Somehow i attached the
[EMAIL PROTECTED] wrote:
>
Does modperl-1.0 also need to have its read functions rewritten in a
similar way?
I ask because Apache::ASP and CGI.pm no longer work happily together
since CGI.pm version 3.01. That is to say, the Apache::ASP example for
demonstrating CGI-compatibility:
http://www.ap
Michael Peppler wrote:
I ran into the same (or a similar) problem that Scott Beuker reported
with CGI.pm truncating POST content in an mp2 setup. In my case the POST
was truncated at around 7500 bytes. A check with tcpdump shows that the
entire POST is correctly sent to apache.
I started by upgr
Helmut Zeilinger wrote:
Hi,
--On Tuesday, March 09, 2004 00:18:22 -0800 Stas Bekman <[EMAIL PROTECTED]>
wrote:
..
on Linux 2.4.22/Apache 2.48/Perl 5.9.0 the compilation of mp 1.99_13
failed (see below).
Is it because of Perl version 5.9.0? Must i downgrade to Perl 5.8.x
again?
It's because you hav
but in "make test" ALL tests fail (See below).
Also below are the outputs of t/REPORT and of t/logs/error_log.
What else can i provide/try?
Regards
Helmut
[make test]
cd "src/modules/perl" && make -f Makefile.modperl
make[1]: Entering directory
`/tmp/install/apache/
*** Packages of interest status:
Apache::Request: -
CGI: 3.04
LWP: 5.65
mod_perl : 1.9912, 1.9912, 1.9913
You have a bunch of older mp2 installs lingering around. I won't be
surprised if you get the wrong libraries loaded. I'd suggest to nuke
any previous mod_perl
Arnaud Blancher wrote:
hi Stas,
here the complete bug report,
Thanks Arnaud,
2. Used Components and their Configuration:
*** mod_perl version 1.9913
[...]
*** Packages of interest status:
Apache::Request: -
CGI: 3.04
LWP: 5.65
mod_perl : 1.9912, 1.9912, 1.9913
You h
Jie Gao wrote:
[...]
We need to write a generic function to resolve localhost and make sure that we
get an ip and not ::1 on the ipv4 systems. If we get ::1 Apache won't start.
Help to accomplish that is very appreciated.
I have spent some time into this and found some interesting things.
On a S
20031114"
#---------
# error_log
#-
# first time: ok
[Mon Mar 15 12:03:15 2004] [notice] caught SIGTERM, shutting down
[Mon Mar 15 12:03:52 2004] [notice] Apache/2.0.48 (Unix)
mod_perl/1.99_13 Perl/v5.8.3 configured --
Arnaud Blancher wrote:
hi all,
i test all my scripts which this version of mod perl
and i have the message :
[notice] child pid 3541 exit signal Segmentation fault (11)
in the error_log all the times but not the first one when i call the script
if i remove
print header();
and put
print "Content-Ty
hi all,
i test all my scripts which this version of mod perl
and i have the message :
[notice] child pid 3541 exit signal Segmentation fault (11)
in the error_log all the times but not the first one when i call the script
if i remove
print header();
and put
print "Content-Type: text/plain\n\n";
it
Swen Schillig wrote:
I figured a few strange outputs while running make test
after a successful compilation of mod_perl-1.99-13
saying that
the server couldn't be started (syntax error at line 27 of
httpd.conf -> Listen localhost:8xxx) (Linux on i386)
or
dubios output for most of t
I figured a few strange outputs while
running make test
after a successful compilation of mod_perl-1.99-13
saying that
the
server couldn't be started (syntax error at line 27 of httpd.conf ->
Listen localhost:8xxx) (Linux on i386)
or
dubios
output for most of the tests (Linux on PP
Hello again,
On Wed, 10 Mar 2004, Charlie Smith wrote:
> What is recommended way to build this into apache.
> We'll need mod_rewrite, mod_perl (with DBD::Oracle), mod_php (with Oracle and
> mysql), mod_ssl. I believe mod_dav comes with Apache 2.
I should have mentioned that you should have chos
Hi there,
On Wed, 10 Mar 2004, Charlie Smith wrote:
> What is recommended way to build this into apache.
> We'll need mod_rewrite, mod_perl (with DBD::Oracle), mod_php (with Oracle and
> mysql), mod_ssl. I believe mod_dav comes with Apache 2.
>
> Should above all work together?
Yes. There's mu
What is recommended way to build this into apache.
We'll need mod_rewrite, mod_perl (with DBD::Oracle), mod_php (with Oracle and
mysql),
mod_ssl. I believe mod_dav comes with Apache 2.
Should above all work together? And what would be recommended way to build
-static or with DSOs?
>>> "Stas B
I get a clean build from CVS now.
--
"The blues are multicolored." -- Dave Lambert
Daniel Risacher [EMAIL PROTECTED]
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org
I'll be using .12 in production in 3 weeks. Just running tests now.
Stas Bekman wrote:
Charlie Smith wrote:
Is this the mod_perl version we should be using with Apache 2 then?
Yes.
Assuming all tests go well?
Yes
What is fate of mp2 at this time?
Once the API is frozen and document
Jie Gao wrote:
[...]
That's great, Jie. Could you rewrite it not to use any external applications,
but pure perl? The problem with external apps is that args and location vary
from platform to platfrom and even from one release to another. Also using
perl we won't need to write a separate implement
[Tue Mar 09 13:12:21 2004] [error] [client 127.0.0.1] can't open
/usr/local/src/mod_perl-1.99_13/t/htdocs/hooks/cleanup: Permission
denied at
/usr/local/src/mod_perl-1.99_13/Apache-Test/lib/Apache/TestUtil.pm
line 96.
[Tue Mar 09 13:12:27 2004] [error] [client 127.0.0.1] can't open
/u
2004] [error] [client 127.0.0.1] can't open
/usr/local/src/mod_perl-1.99_13/t/htdocs/hooks/cleanup: Permission denied at
/usr/local/src/mod_perl-1.99_13/Apache-Test/lib/Apache/TestUtil.pm line 96.
[Tue Mar 09 13:12:27 2004] [error] [client 127.0.0.1] can't open
/usr/local/src/mod_perl-
No need for any extra info as I can see all these errors with a fresh package
run under root:
t/directive/perl.t 84 50.00% 2-3 6-7
t/directive/perldo.t 142 14.29% 11 14
t/hooks/cleanup.t 21 50.00% 2
t/hooks/cleanup2.t
Daniel Risacher wrote:
I get these errors with yesterday's CVS (some of which are the same
that Arnaud saw):
t/modules/include...ok 2/6# Failed test 4 in t/modules/include.t at line 32 fail #2
# Failed test 5 in t/modules/include.t at line 32 fail #3
t/modules/include.
On Tue, 9 Mar 2004, Steve Hay wrote:
> Steve Hay wrote:
>
> >I'll try chopping some of the new (post _12) tests out to see if I can
> >get it working again.
> >
> If I remove:
>
> t/htdocs/vhost/startup.pl
> t/response/TestVhost/config.pm
> t/vhost/config.t
>
> then run "t/TEST -conf"
[Tue Mar 09 13:12:21 2004] [error] [client 127.0.0.1] can't open
/usr/local/src/mod_perl-1.99_13/t/htdocs/hooks/cleanup: Permission denied at
/usr/local/src/mod_perl-1.99_13/Apache-Test/lib/Apache/TestUtil.pm line 96.
[Tue Mar 09 13:12:27 2004] [error] [client 127.0.0.1] can't open
/us
I get these errors with yesterday's CVS (some of which are the same
that Arnaud saw):
t/modules/include...ok 2/6# Failed test 4 in t/modules/include.t
at line 32 fail #2
# Failed test 5 in t/modules/include.t at line 32 fail #3
t/modules/include...FAILED
/home/installation-publishing/modules/unix/perl5.8/apache/mod_perl-1.99_13/t/TEST
-clean
APACHE_TEST_GROUP= APACHE_TEST_HTTPD= APACHE_TEST_PORT=
APACHE_TEST_USER= APACHE_TEST_APXS= \
/usr/bin/perl -Iblib/arch/Apache2 -Iblib/lib/Apache2 \
t/TEST -bugreport -verbose=0
[warning] setting ulimit to allo
Steve Hay wrote:
>I'll try chopping some of the new (post _12) tests out to see if I can
>get it working again.
>
If I remove:
t/htdocs/vhost/startup.pl
t/response/TestVhost/config.pm
t/vhost/config.t
then run "t/TEST -conf" and then try "nmake test" again, then it's all
OK with 20
Stas Bekman wrote:
>Steve Hay wrote:
>
>
>>I have to
>>increase ThreadsPerChild in the mpm_winnt.c section
>>(Apache-Test/lib/Apache/TestConfig.pm) to some value higher than 20.
>>I'm not sure how much higher it needs to be, but 50 works for me.
>>
>>
>
>the worker mpm works just fine wi
Jie Gao wrote:
On Sat, 6 Mar 2004, Stas Bekman wrote:
Date: Sat, 06 Mar 2004 15:25:35 -0800
From: Stas Bekman <[EMAIL PROTECTED]>
To: Jie Gao <[EMAIL PROTECTED]>
Cc: mod_perl Mailing List <[EMAIL PROTECTED]>
Subject: Re: [RELEASE CANDIDATE] please test mod_perl-1.99_13-dev.ta
Thank you all for testing this release candidate.
1.99_13 was released a few hours ago.
__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[E
Dr. Helmut Zeilinger wrote:
Hi,
on Linux 2.4.22/Apache 2.48/Perl 5.9.0 the compilation of mp 1.99_13 failed
(see below).
Is it because of Perl version 5.9.0? Must i downgrade to Perl 5.8.x again?
It's because you have an old 5.9.0. Only the very latest blead perl is
supported. Upgrade to the curr
If anyone is interested, I've created FC1 RPMs of mod_perl-1.99_13.
They are available at http://buscaluz.org/rpms/
I'm not currently involved in the Fedora project. I created these RPMs
for my convenience and have decide to share them. My system is mostly--
but not completely--st
Charlie Smith wrote:
Is this the mod_perl version we should be using with Apache 2 then?
Yes.
Assuming all tests go well?
Yes
What is fate of mp2 at this time?
Once the API is frozen and documented, and this todo list [1] is cleaned up we
will release 2.0. You can help to make this happen
Is this the
mod_perl version we should be using with Apache 2 then? Assuming all tests
go well? What is fate of mp2 at this time? Is it near
production level yet?>>> "Stas Bekman" <[EMAIL PROTECTED]>
03/05/04 07:46PM >>>A release candidate for m
The uploaded file
mod_perl-1.99_13.tar.gz
has entered CPAN as
file: $CPAN/authors/id/S/ST/STAS/mod_perl-1.99_13.tar.gz
size: 1197628 bytes
md5: e8945611cae2fe797ae4bb198c0285b6
and is also available from:
http://apache.org/dist/perl/mod_perl-1.99_13.tar.gz
http://apache.org
On Fri, 05 Mar 2004 18:46:03 -0800
Stas Bekman <[EMAIL PROTECTED]> wrote:
> A release candidate for mod_perl-1.99_13 is available:
>
> http://apache.org/~stas/mod_perl-1.99_13-dev.tar.gz
>
> Please test and report any failures to this list.
Hi Stas,
all tests successf
Steve Hay wrote:
Randy Kobes wrote:
All tests successful on my Win32: Apache/2.0.48 and
perl-5.8.3 (ActivePerl 809).
Not quite so for me (WinXP / MSVC6 / 2.0.48 / 5.8.3) -- I have to
increase ThreadsPerChild in the mpm_winnt.c section
(Apache-Test/lib/Apache/TestConfig.pm) to some value higher
On Mon, 8 Mar 2004, Steve Hay wrote:
> Randy Kobes wrote:
>
> >All tests successful on my Win32: Apache/2.0.48 and
> >perl-5.8.3 (ActivePerl 809).
> >
> Not quite so for me (WinXP / MSVC6 / 2.0.48 / 5.8.3) -- I have to
> increase ThreadsPerChild in the mpm_winnt.c section
> (Apache-Test/lib/Apache
On Sun, Mar 07, 2004 at 06:35:14PM -0800, Stas Bekman wrote:
> The Doctor wrote:
> >On Fri, Mar 05, 2004 at 06:46:03PM -0800, Stas Bekman wrote:
> >
> >>A release candidate for mod_perl-1.99_13 is available:
> >>
> >>http://apache.org/~stas/mod_perl-1
Randy Kobes wrote:
>All tests successful on my Win32: Apache/2.0.48 and
>perl-5.8.3 (ActivePerl 809).
>
Not quite so for me (WinXP / MSVC6 / 2.0.48 / 5.8.3) -- I have to
increase ThreadsPerChild in the mpm_winnt.c section
(Apache-Test/lib/Apache/TestConfig.pm) to some value higher than 20.
I'm
The Doctor wrote:
On Fri, Mar 05, 2004 at 06:46:03PM -0800, Stas Bekman wrote:
A release candidate for mod_perl-1.99_13 is available:
http://apache.org/~stas/mod_perl-1.99_13-dev.tar.gz
Please test and report any failures to this list.
If everything goes well, 1.99_13 will be released on
On Fri, Mar 05, 2004 at 06:46:03PM -0800, Stas Bekman wrote:
> A release candidate for mod_perl-1.99_13 is available:
>
> http://apache.org/~stas/mod_perl-1.99_13-dev.tar.gz
>
> Please test and report any failures to this list.
>
> If everything goes well, 1.99_13 will b
All tests successful on my Win32: Apache/2.0.48 and
perl-5.8.3 (ActivePerl 809).
--
best regards,
randy
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Jie Gao wrote:
[...]
I've got it work. What I did was to comment out the ipv6 entry in Solaris's
Internet host table:
% more /etc/inet/ipnodes
#
# Internet host table
#
#::1localhost
127.0.0.1 localhost
/etc/nsswitch.conf has the following as default:
ipnodes:files
Neverthel
OK, here you are:
Thanks, Jie. So we are on Solaris. It doesn't sound like a mod_perl problem,
but Apache and/or Apache-Test's one.
[Sat Mar 06 15:41:32 2004] [info] base server + 16 vhosts ready to run tests
...(126)Cannot assign requested address: make_sock: could not bind to address
[::1]:85
Jie Gao wrote:
I also assume that you are running on ipv6, because of [::1]:8549
Ah! That could be the problem, as I am _not_ running on ipv6: no ipv6
interfaces are up or even configured. How did the test get it?
Sorry, Jie I can't do any guesses before you post a proper bug report.
I should h
Jie Gao wrote:
SunOS banquo 5.9 Generic_112233-11 sun4u sparc
Apache/2.0.48 mod_perl/1.99_13-dev Perl/v5.8.3 (threaded)
Make test fails:
% gmake test
...
[warning] root mode: changing the files ownership to 'nobody' (60001:60001)
[warning] testing whether 'nobody' is able t
On Sat, 2004-03-06 at 03:18, Andrew Wyllie wrote:
> All tests passed on FreeBSD-5.2, Perl-5.8.3, Apache-2.0.48
>
All tests also passed on Linux 2.4.20-gentoo-r9, Perl-5.8.3,
Apache-2.0.48! (threads not enabled)
Thanks Stas!
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http
All tests passed on FreeBSD-5.2, Perl-5.8.3, Apache-2.0.48
Thanks!
Andrew
Stas Bekman wrote:
A release candidate for mod_perl-1.99_13 is available:
http://apache.org/~stas/mod_perl-1.99_13-dev.tar.gz
Please test and report any failures to this list.
If everything goes well, 1.99_13 will
All tests passed on FreeBSD-5.2
Thanks!
Andrew
Stas Bekman wrote:
A release candidate for mod_perl-1.99_13 is available:
http://apache.org/~stas/mod_perl-1.99_13-dev.tar.gz
Please test and report any failures to this list.
If everything goes well, 1.99_13 will be released on Tuesday, so
A release candidate for mod_perl-1.99_13 is available:
http://apache.org/~stas/mod_perl-1.99_13-dev.tar.gz
Please test and report any failures to this list.
If everything goes well, 1.99_13 will be released on Tuesday, so those who do
mod_perl at work can test on Monday and those at home over
On Sun, 2004-01-11 at 22:39, John DeBenedette wrote:
> The following works flawlessly under CGI but when attempting under Registry
> as module or PerlRun as script, it works once perfectly, then continues to
> work with no discernable error but causes the listening server's accept()
> process to go
John DeBenedette wrote:
correction of typo in my example at INET->new
$dbpoolport s/b $poolport
$dbhost s/b $host
What would it take to paste the real minimal script that fails? It's full of
problems. You have '>' in:
$poolport, Proto => "tcp", Type => SOCK_STREAM) > or die "could not
you don'
correction of typo in my example at INET->new
$dbpoolport s/b $poolport
$dbhost s/b $host
-Original Message-
From: John DeBenedette [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 11, 2004 10:40 PM
To: '[EMAIL PROTECTED]'
Subject: mod_perl 1.99_13 - IO:Socket::INET works only
SERVER_SOFTWARE = "Apache/2.0.48 (Win32) mod_perl/1.99_13-dev Perl/v5.8.2
PHP/4.3.4 mod_ssl/2.0.48 OpenSSL/0.9.7c"
The following works flawlessly under CGI but when attempting under Registry
as module or PerlRun as script, it works once perfectly, then continues to
work with no discern
88 matches
Mail list logo
