Return-Path: Delivered-To: apmail-httpd-bugs-archive@www.apache.org Received: (qmail 57309 invoked from network); 2 Apr 2004 09:50:29 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Apr 2004 09:50:29 -0000 Received: (qmail 38876 invoked by uid 500); 2 Apr 2004 09:50:03 -0000 Delivered-To: apmail-httpd-bugs-archive@httpd.apache.org Received: (qmail 38845 invoked by uid 500); 2 Apr 2004 09:50:03 -0000 Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: "Apache HTTPD Bugs Notification List" Delivered-To: mailing list bugs@httpd.apache.org Received: (qmail 38828 invoked from network); 2 Apr 2004 09:50:02 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 2 Apr 2004 09:50:02 -0000 Received: (qmail 22783 invoked by uid 50); 2 Apr 2004 09:50:55 -0000 Date: 2 Apr 2004 09:50:55 -0000 Message-ID: <20040402095055.22782.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: bugs@httpd.apache.org Cc: Subject: DO NOT REPLY [Bug 28086] - Apache 2.0.49 crashes on graceful restart X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28086 Apache 2.0.49 crashes on graceful restart noackjr@alumni.rice.edu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From noackjr@alumni.rice.edu 2004-04-02 09:50 ------- I still see this with PHP 4.3.6-RC1 (released 2 days after fix supposedly was in PHP CVS). Also, there is no mention of the fix in NEWS or Changelog nor was I able to find it in CVS (it could still be there, I just couldn't find one). In any case, this doesn't appear to be fixed yet. Are we sure this is a PHP problem? Someone posted to the PHP bug listed above that neither PHP 4.3.5 or 5.0.0-RC1 have problems with Apache 2.0.48, but both exhibit this broken behavior with Apache 2.0.49. In any case, I'm reopening. Anyone who can shed light on this gets the prize... --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org For additional commands, e-mail: bugs-help@httpd.apache.org