Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Message-ID: <077401c0a18a$dd5926a0$e4421b09@raleigh.ibm.com>
From: "Bill Stoddard" <bill@wstoddard.com>
To: <new-httpd@apache.org>
References: <Pine.LNX.4.33.0102272203370.8499-100000@twinlark.arctic.org>
Subject: Re: Problem found in perform_idle_server_maintenance on prefork.
Date: Wed, 28 Feb 2001 08:32:15 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


----- > i'm pretty sure SIGWINCH is just the SIGUSR1 replacement right?  it
tells
> the child to die as soon as is convenient.  so the process really only
> needs to die off after it's fully initialised.  if so then all of the
> above is avoided by using signal handlers in the only way they're safe to
> use:  to tweak a global variable.  (1.3's USR1 handler is almost that
> simple.)

Jeff Trawick made this same point yesterday in a hall talk.

>
> and actually that graceful die flag might as well live in the scoreboard.
> i can't remember why the graceful die flag doesn't live in the scoreboard
> in 1.3... maybe i just never thought of it.  hrm.  i bet i just didn't
> bother to move it there because 1.3 code had to be signal aware anyhow.
> you may want to move this to the scoreboard in 2.0 to eliminate the
> SIGWINCH in the children, it'll mean fewer potential problems with
> non-signal aware 3rd party code.
>

+1

Bill