httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@apache.org
Subject cvs commit: httpd-2.0 STATUS
Date Fri, 07 Dec 2001 15:41:00 GMT
rbb         01/12/07 07:41:00

  Modified:    .        STATUS
  Log:
  Add a note about terminating the server.
  
  Revision  Changes    Path
  1.350     +9 -1      httpd-2.0/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/STATUS,v
  retrieving revision 1.349
  retrieving revision 1.350
  diff -u -r1.349 -r1.350
  --- STATUS	2001/12/07 15:33:58	1.349
  +++ STATUS	2001/12/07 15:41:00	1.350
  @@ -1,5 +1,5 @@
   APACHE 2.0 STATUS:						-*-text-*-
  -Last modified at [$Date: 2001/12/07 15:33:58 $]
  +Last modified at [$Date: 2001/12/07 15:41:00 $]
   
   Release:
   
  @@ -99,6 +99,14 @@
         Reasons include sole-function servers that need to die if
         an external dependency (e.g., a database) fails, et cetera.
         Perhaps something in the (ever more abused) scoreboard?
  +	rbb:  I don't believe the scoreboard is the correct mechanism
  +	for this.  We already have a pipe that goes between parent
  +	and child for graceful shutdown events, along with an API that
  +	can be used to send a message down that pipe.  In threaded MPMs,
  +	it is easy enough to make that one pipe be used for graceful
  +	and graceless events, and it is also easy to open that pipe
  +	to both parent and child for writing.  Then we just need to figure
  +	out how to do graceless on non-threaded MPMs.
   
       * revamp the input filter behavior, per discussions since
         February (and especially at the hackathon last
  
  
  

Mime
View raw message