2.0.14 : rolled March 7, 2000
scheduled for release March 10, 2000
Erm, what's today's date?
:)
On Thu, 22 Mar 2001, David Reid wrote:
2.0.14 : rolled March 7, 2000
scheduled for release March 10, 2000
Erm, what's today's date?
:)
The 22nd, but the tarballs were released on the 10th. :-) I forgot to
edit the STATUS file.
And what year is it this
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] wrote:
On Thu, 22 Mar 2001, Jeroen Massar wrote:
On Thu, 22 Mar 2001, David Reid wrote:
2.0.14 : rolled March 7, 2000
scheduled for release March 10, 2000
Erm, what's today's date?
:)
The
With a far greater understanding than I had 24 hours ago...
Is there any reason not to just _Drop_ the BindAddress directive and strictly
use the Listen directive for Apache 2.0?
I'd even go so far as depreciate the Port directive in favor of a more
decorated ServerName directive
From: "Rodent of Unusual Size" [EMAIL PROTECTED]
Sent: Thursday, March 22, 2001 9:55 AM
Bill has discovered an interesting problem with ErrorDocument 400
handling..
ErrorDocument 400 "string
works every time.
ErrorDocument 400 /local-URI
but does NOT work for the following; it
"Bill Stoddard" [EMAIL PROTECTED] writes:
Running 2.0 on AIX with the threaded MPM. Start Apache as root. ps -ef |
grep
httpd shows one process running as root and the remaining processes
running as
nobody with a PPID of the parent process. Fine so far. If I load the
server
down, the
"William A. Rowe, Jr." [EMAIL PROTECTED] writes:
With a far greater understanding than I had 24 hours ago...
Is there any reason not to just _Drop_ the BindAddress directive and strictly
use the Listen directive for Apache 2.0?
We already did as near as I can tell ("grep -i BindAddress" in
"Bill Stoddard" [EMAIL PROTECTED] writes:
Haven't fully debugged this yet, but it appears that a child process is
forking processses. When the child dies, the PPID of the forked process
changes to 1. Will spend some time this afternoon tracking this one
down.
Could it be mod_cgid perhaps?
I'd even go so far as depreciate the Port directive in favor of a more
decorated ServerName directive (joespages.org:80) where port 80 is
assumed.
If we don't really need Port ('cause we don't need a port number in
addition to what is specified on the Listen statement), then I'm all
From: "Jeff Trawick" [EMAIL PROTECTED]
Sent: Thursday, March 22, 2001 11:15 AM
"William A. Rowe, Jr." [EMAIL PROTECTED] writes:
I'd even go so far as depreciate the Port directive in favor of a more
decorated ServerName directive (joespages.org:80) where port 80 is
assumed.
If we
Disabled mod_cgid and I still see the problem.
Bill
"Bill Stoddard" [EMAIL PROTECTED] writes:
Haven't fully debugged this yet, but it appears that a child process is
forking processses. When the child dies, the PPID of the forked process
changes to 1. Will spend some time this
On Wed, 21 Mar 2001, Stanislav Rost wrote:
A little about the setup: two P2-400's stressing another P2-400 with
400-500 concurrent ongoing downloads of large files at any given
instant of time (so high concurrency levels are implicit). Apache is
directed to create at least that many
Okay, I understand what's happening, just need to give the fix a bit of
thought. Skipping over the boring details, we are not handling the main
thread in child_main() correctly. When workers_may_exit is set, the child
worker threads are cleaned up, but the child_main() thread returns to
On Thu, 22 Mar 2001, Peter J. Cranstone wrote:
Any chance of someone running this same test using mod_gzip and compressing
the data in real time for each request?
If it's a 1MB *text* file we should compress it down by roughly 75% - 80%
and then your bandwidth figure will change.
eh..
Blue and many others,
Thanks for the response. You are right, I need to provide a few more
details.
The files are 10 MBs each, the Apache version is 1.2.12 (should I
upgrade? were there scalability enhancements since then?), the Linux
kernel version is 2.2.19pre16 (unfortunately, I cannot go
Greg Ames wrote:
"Paul J. Reder" wrote:
@@ -568,7 +579,7 @@
apr_signal(SIGHUP, just_die);
apr_signal(SIGTERM, just_die);
-while (!ap_graceful_stop_signalled()) {
+while ((!ap_graceful_stop_signalled()) (!ap_idle_die_signalled())) {
This is part of the
Hello everyone,
Actually i don`t know if this is the right list, but i haven`t
found a better to ask this question. For each user i run a
copy of apache. I would like apache to be able to "register its
processes" not like it does, but in the following way (for
example)
On 22 Mar 2001 [EMAIL PROTECTED] wrote:
stoddard01/03/22 11:29:10
Modified:.CHANGES
server/mpm/threaded threaded.c
Log:
Exit the child main thread in make_child on child exit. This fixes a problem
where the child main thread was looping in
Hi Bill,
2. There's also an extra read on the request socket just
before the httpd sends the response, and another after
the logger runs; both of these fail with EAGAIN. (I saw
this with an HTTP/1.1 client that supports keepalives, so
the last failed read was
Three more messages from the larger community posted to new-httpd over
the last few days. Ezmlm is configured to divert postings from
non-subscribers to the moderator, that's currently me. I have replied
to all of these.
- ben
Message-ID: [EMAIL PROTECTED]
Date:
20 matches
Mail list logo
