Received: (qmail 19753 invoked by uid 2012); 2 Aug 1998 12:48:40 -0000 Message-Id: <19980802124840.19752.qmail@hyperreal.org> Date: 2 Aug 1998 12:48:40 -0000 From: Ben Laurie Reply-To: ben@algroup.co.uk To: apbugs@hyperreal.org Subject: subprocess cleanup can fail on restart/shutdown X-Send-Pr-Version: 3.2 >Number: 2762 >Category: apache-api >Synopsis: subprocess cleanup can fail on restart/shutdown >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: feedback >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Sun Aug 2 05:50:00 PDT 1998 >Closed-Date: >Last-Modified: Wed May 24 10:44:08 PDT 2000 >Originator: ben@algroup.co.uk >Release: 1.3.1 >Organization: >Environment: Any? >Description: If kill_after_timeout is used in an ap_spawn_child, using the pconf pool, then the child is not killed when the server is killed. Changing to kill_always appears to fix the problem. At least, I'm pretty sure that's what's happening. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: coar State-Changed-When: Thu Apr 29 10:31:16 PDT 1999 State-Changed-Why: [This is a standard response.] This Apache problem report has not been updated recently. Please reply to this message if you have any additional information about this issue, or if you have answers to any questions that have been posed to you. If there are no outstanding questions, please consider this a request to try to reproduce the problem with the latest software release, if one has been made since last contact. If we don't hear from you, this report will be closed. If you have information to add, BE SURE to reply to this message and include the apbugs@Apache.Org address so it will be attached to the problem report! From: Aidan Cully To: apbugs@apache.org Cc: Subject: apache-api/2762: subprocess cleanup can fail on restart/shutdown Date: Fri, 21 May 1999 18:19:38 -0400 This has been happening here as well, with Apache 1.3.5dev. I've got, in my httpd.conf, the line ErrorLog "|/usr/local/bin/aplog.pl" . As you all probably know, apache sees this and runs it using /bin/sh as a wrapper, like so: /bin/sh -c '/usr/local/bin/aplog.pl' . When apache gets kill -HUPped, it _does_ send the SIGTERM, followed by the SIGKILL to the 'sh' process, which dies, but then the aplog.pl process doesn't get killed along with it. You can work around it by substituting ErrorLog "|exec /usr/local/bin/aplog.pl" for ErrorLog "|/usr/local/bin/aplog.pl" . --aidan -- Aidan Cully "Chihuahuahuahuahua." Panix Staff --The Sugercubes aidan@panix.com Comment-Added-By: coar Comment-Added-When: Wed May 24 10:44:07 PDT 2000 Comment-Added: [This is a standard response.] This Apache problem report has not been updated recently. Please reply to this message if you have any additional information about this issue, or if you have answers to any questions that have been posed to you. If there are no outstanding questions, please consider this a request to try to reproduce the problem with the latest software release, if one has been made since last contact. If we don't hear from you, this report will be closed. If you have information to add, BE SURE to reply to this message and include the apbugs@Apache.Org address so it will be attached to the problem report! >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]