Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 45155 invoked by uid 500); 30 Aug 2001 13:53:27 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 45135 invoked from network); 30 Aug 2001 13:53:27 -0000 Importance: Normal Subject: Re: please make SIG_GRACEFUL configurable To: dev@httpd.apache.org X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000 Message-ID: From: "RCHAPACH Rochester" Date: Thu, 30 Aug 2001 08:52:53 -0500 X-MIMETrack: Serialize by Router on d27ml104/27/M/IBM(Release 5.0.8 |June 18, 2001) at 08/30/2001 08:52:54 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: X-UID: 1608 I agree. AS/400 supports signals but SIGWINCH is not supported. We end up using SIGUSR1 anyway. Rob Simonson simo@us.ibm.com "Roy T. Fielding" on 08/29/2001 08:21:33 PM This has been on my to-do list for ages. The decision to change from SIGUSR1 to SIGWINCH just because a particular old version of Linux threads happens to suck was a bad decision. Hard-coding the value within a bunch of places in httpd was just bad coding. I would really appreciate it if someone coded up a patch to add an AP_SIG_GRACEFUL definition, apply it everywhere in the code (and in the control scripts), and then make it configurable using configure [default=SIGUSR1]. To make it even better, we should have a way to signal it using httpd itself httpd restart httpd graceful httpd stop would check for an existing process and send it the appropriate signal. That way we wouldn't be spreading implementation assumptions throughout the support code. ....Roy