Return-Path: 
 <new-httpd-return-18483-apmail-new-httpd-archive=apache.org@apache.org>
Delivered-To: apmail-new-httpd-archive@apache.org
Received: (qmail 7773 invoked by uid 500); 8 Aug 2001 15:17:08 -0000
Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
list-help: <mailto:new-httpd-help@apache.org>
list-unsubscribe: <mailto:new-httpd-unsubscribe@apache.org>
list-post: <mailto:new-httpd@apache.org>
Delivered-To: mailing list new-httpd@apache.org
Received: (qmail 7752 invoked from network); 8 Aug 2001 15:17:08 -0000
X-Authentication-Warning: cobra.cs.Virginia.EDU: jcw5q owned process doing -bs
Date: Wed, 8 Aug 2001 11:17:08 -0400 (EDT)
From: Cliff Woolley <cliffwoolley@yahoo.com>
X-X-Sender: <jcw5q@cobra.cs.Virginia.EDU>
To: <new-httpd@apache.org>
Subject: Re: Currently known issues with 2.0.23
In-Reply-To: <01080807340502.03684@koj.rkbloom.net>
Message-ID: <Pine.GSO.4.32.0108081110410.7199-100000@cobra.cs.Virginia.EDU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N
Status: O
X-Status: 
X-Keywords: 
X-UID: 240

On Wed, 8 Aug 2001, Ryan Bloom wrote:

> On Tuesday 07 August 2001 23:53, Cliff Woolley wrote:
> > --------------------------------------------------------------
> > Known issues with 2.0.23:
> >
> > 1) Win9x, WinME, and Netware do not yet work.
> > 2) Unix: The threaded MPM might take longer than expected to restart or
> >    shutdown on very-low-traffic (near idle) servers.  This is due to the
>
> I dislike this.  It's the "near idle" that bothers me.  We rely on the
> OS to never starve a thread to get any restart or shutdown.  The
> server could easily be getting hit moderately, and not shutdown
> correctly.  I don't want to see us down-play the problem, and have
> people think that the server is working when it isn't.  There is a
> real chance that an admin can do a graceful restart, and still be
> serving requests off the old config for a very long time.

How about "servers getting very few requests" instead of
"very-low-traffic (near idle) servers"?

I threw the "near idle" bit in there to emphasize that (a) it effects
people running test servers that have nobody connecting to them at all,
and (b) that our definition here of "very low traffic" is not 100 conn/sec
as opposed to 1000 conn/sec, but more on the order of just a handful of
conn/sec, since 100 conn/sec might be seen as very low traffic by some
administrators.  ;-)

As per Greg's suggestion, I'll also try to split up that paragraph into
two to make it easier to read.

As for the shutdown issue... is it really an issue?  Generally speaking,
when I do an apachectl graceful, I can see the issue of which you speak,
but when I do an apachectl shutdown, it just goes.  Maybe I'm missing it.
<shrug>

Also, as I mentioned last night, ungraceful for threaded seems to be
broken.

Thanks,
Cliff

--------------------------------------------------------------
   Cliff Woolley
   cliffwoolley@yahoo.com
   Charlottesville, VA