Stas Bekman wrote:
William McKee wrote:
On Wed, Jan 14, 2004 at 08:41:01PM -0800, Stas Bekman wrote:
Cool, now I get the thing running.
Great. Are you getting any failures? Please read my notes in
testnotes.txt.
Yes. I will look at the failures soonish.
I don't have apache 1.3 with ssl so I
William McKee wrote:
--- testing.pod.orig 2004-01-14 22:15:37.0 -0500
+++ testing.pod 2004-01-14 21:16:30.0 -0500
@@ -361,7 +358,7 @@
in order to try to detect as many problems as possible during the
testing process, it's may be useful to run tests in different orders.
-This if
On Fri, Jan 16, 2004 at 01:03:00PM -0500, William McKee wrote:
On Thu, Jan 15, 2004 at 04:24:41PM -0800, Stas Bekman wrote:
I don't have apache 1.3 with ssl so I can't test it. And it doesn't quite
work with apache/mp 2.0 because you have hardcoded mp1 API. Please see the
porting doc:
On Thu, Jan 15, 2004 at 09:03:54PM -0800, Stas Bekman wrote:
I didn't commit this part. I'm not sure we want to duplicate the porting
guide in this document. Instead of duplicating things, I've added a section
telling that this document uses mp2 in examples and gave a pointer to the
chapter
On Fri, Jan 16, 2004 at 02:01:15PM -0500, Geoffrey Young wrote:
you can use have_lwp() to check for LWP support. have_module() is handy too.
Thanks.
OK. FYI, I didn't see anything about this in the docs. I looked at the
t/ dir in Apache::Test and only see request.t and ping.t. The
Honestly, I am trying my best. The problems I am encountering are
changing perspective from a cgi to a mod_perl framework which thus
entails learning lots more about the Apache server than I've ever known
before. My apologies if you think these questions are inane or
off-topic.
no, I'm
On Fri, Jan 16, 2004 at 02:30:45PM -0500, Geoffrey Young wrote:
no, I'm sorry - I didn't mean to sound so harsh. it just seemed to me that
this was becoming a very long thread comprised mostly of things that I knew
were answered already. apparentlly, not clearly enough, though :)
Thanks for
On Fri, Jan 16, 2004 at 02:30:45PM -0500, Geoffrey Young wrote:
if you're feeling a bit overwhelmed but have Apache-Test installed, I'd
suggest that you start with this
http://perl.apache.org/~geoff/bug-reporting-skeleton-mp1.tar.gz
examine it, run it, and get a feel for how the test
On Thu, Jan 15, 2004 at 05:08:39PM -0800, Stas Bekman wrote:
strange, I saw it once and could never reproduce it again. What is the
sequence of commands when you get it?
That is interesting. Right now, I'm playing with Geoff's
bug-reporting-skeleton-mp1 running my my Apache 1.3.29 server with
On Fri, Jan 16, 2004 at 12:45:01AM +0100, Erik Abele wrote:
On 15.01.2004, at 09:54, [EMAIL PROTECTED] wrote:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26149
Apache 2.0.48 won't load Tomcat 4.1.29 in-process via JK2
--- Additional Comments From [EMAIL PROTECTED] 2004-01-15
Hi to all,
I just got a fresh Linux LPAR on one of our iSeries loaded
with SUSE SLES 8.0.
Everything goes right (go job Rochester/Austin IBMer folks)
but the pre installed Apache is a 1.3.26.
I'd like to use an Apache 2.0.x one (for mod_deflate) and wonder
if there is such RPM / SPEC available
Henri Gomez wrote:
I'd like to use an Apache 2.0.x one (for mod_deflate) and wonder
if there is such RPM / SPEC available somewhere (I've got
problem with SUSE .spec).
no idea
Alternativly, did there is some specific stuff for this PowerPC
box and what's the prefered mode (worker or prefork ?)
* unescaped error logs seem to be essential for some folks
backport -DAP_UNSAFE_ERROR_LOG_UNESCAPED to 2.0 and 1.3
server/log.c: r1.139, r1.140
-+1: nd
++1: nd, stas
should this get another vote, I have patches for 2.0 and 1.3 ready.
--Geoff
Index:
I'm interested in doing some scalability testing with worker on Linux to see
what the O(1) scheduler and new pthread library buys us, and what happens with
different values for ThreadsPerChild. I decided to use a simple handler that
just nanosleep()s for a variable amount of time controlled by
...which is the same way we enable mod_status and mod_info. The key
thing here is that the URIs to access a Location enabled handler do not
map to the filesystem, so the directory walk is a waste of cycles. So
what can we do about it?
isn't that what map_to_storage is for?
Geoffrey Young wrote:
...which is the same way we enable mod_status and mod_info. The key
thing here is that the URIs to access a Location enabled handler do not
map to the filesystem, so the directory walk is a waste of cycles. So
what can we do about it?
isn't that what map_to_storage is
WHat happens if the handler DECLINES the request and do we care?
Bill
[EMAIL PROTECTED] wrote:
I'm interested in doing some scalability testing with worker on Linux to
see what the O(1) scheduler and new pthread library buys us, and what
happens with different values for ThreadsPerChild. I
Bill Stoddard wrote:
WHat happens if the handler DECLINES the request
My guess is that the default handler will be called, try to open a non-existant
file and send back a 404. I'll find out.
and do we care?
If it seg faults, violates protocol or something similar, I care. Other than
that I
[EMAIL PROTECTED] wrote:
Bill Stoddard wrote:
WHat happens if the handler DECLINES the request
My guess is that the default handler will be called, try to open a
non-existant file and send back a 404. I'll find out.
Make sure file 'silly' exists in documentroot and make sure it has access
Bill Stoddard wrote:
mod_status and mod_info both are enabled via Location containers.
mod_status never DECLINEs if it is the handler. mod_info DECLINEs if
the method isn't GET. Let me see what happens if I send mod_info some
other method.
My not so well formed thoughts are that if a
[EMAIL PROTECTED] wrote:
Bill Stoddard wrote:
WHat happens if the handler DECLINES the request
My guess is that the default handler will be called, try to open a
non-existant file and send back a 404. I'll find out.
and do we care?
If it seg faults, violates protocol or something similar,
Bill Stoddard wrote:
WHat happens if the handler DECLINES the request
My guess is that the default handler will be called, try to open a
non-existant file and send back a 404. I'll find out.
Make sure file 'silly' exists in documentroot and make sure it has
access protections coded in a
Geoffrey Young wrote:
Bill Stoddard wrote:
My not so well formed thoughts are that if a module claims it should
handle a request based on a SetHandler directive in a Location
directive, the server should not allow that handler to DECLINE the
request. Putting it another way, if the handler claims
On Fri, 16 Jan 2004, Lars Eilebrecht wrote:
According to Gerardo Reynaga:
Is there a way to pass directives to httpd
once the server is running?
How about using a graceful restart?
Would that be feasible in your case?
Graceful restart (along with HUP restart and even stop) fails
This patch basically computes the average response time and adds X
ms/request response time where X is the response time in milliseconds
to the mod_status display
It works by taking the average of response times of threads who
processed a request within the last RESPTIME_WINDOW_SECS seconds. I
25 matches
Mail list logo
