Return-Path: X-Original-To: apmail-httpd-dev-archive@www.apache.org Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6B15F10CE6 for ; Fri, 26 Dec 2014 06:05:32 +0000 (UTC) Received: (qmail 26133 invoked by uid 500); 26 Dec 2014 06:05:32 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 26073 invoked by uid 500); 26 Dec 2014 06:05:32 -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: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 26063 invoked by uid 99); 26 Dec 2014 06:05:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Dec 2014 06:05:31 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of graham.dumpleton@gmail.com designates 209.85.216.49 as permitted sender) Received: from [209.85.216.49] (HELO mail-qa0-f49.google.com) (209.85.216.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Dec 2014 06:05:06 +0000 Received: by mail-qa0-f49.google.com with SMTP id dc16so6804419qab.36 for ; Thu, 25 Dec 2014 22:05:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=U+7zbbDLM4CgyIq99nBzhbyt3Ty/+l/tHu4gk6TnXRg=; b=Hz1kIuIizbBWObtuHCKQq3ArbHQ5mm2yCSFJyA5SbgUKm/um4GoWbZGoyzde1HNVLf lbMIAdbzUnl5thBYUGr8B6ANZDJAX8xSe8+bBrTHWxGl3HfeidfdmKa1usXVnRkLaEjl m/bLVp2FAwfyHShFjKjAwI8gdT1JSk2OO9DBsrWMokRBa6eKov4mIQ6NVbHqsYT0Yep2 olUSjGLpVU/PeeQTjtbsWXuydVaF9rStdFj7eQnxe/F01aSnwoE8NKhR8bDWF5xrV+UN ip4iToXY5hugL80kixpnfHh9WKwzZ6bJ6uTXNJU/1oM0UBDN3P03bVArIlSAvlQUyNyP o4SA== MIME-Version: 1.0 X-Received: by 10.140.80.136 with SMTP id c8mr42183286qgd.30.1419573905482; Thu, 25 Dec 2014 22:05:05 -0800 (PST) Sender: graham.dumpleton@gmail.com Received: by 10.140.30.5 with HTTP; Thu, 25 Dec 2014 22:05:05 -0800 (PST) In-Reply-To: <7E119A0E-3885-44F3-ADEE-6D66147B17D2@profihost.ag> References: <7E119A0E-3885-44F3-ADEE-6D66147B17D2@profihost.ag> Date: Fri, 26 Dec 2014 17:05:05 +1100 X-Google-Sender-Auth: C0ZapT9KyOG8pAc4d2rigS1dRRk Message-ID: Subject: Re: mod_fcgid kill all subprocesses in reload From: Graham Dumpleton To: "dev@httpd.apache.org" Content-Type: multipart/alternative; boundary=001a11c120a45e6d09050b184e40 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c120a45e6d09050b184e40 Content-Type: text/plain; charset=UTF-8 Sounds like it would perhaps be for the same reason as mod_wsgi has issues with that sort of thing. Only Apache child worker processes get special dispensation as far as graceful shutdowns or reloads are concerned. If instead a module creates additional processes using the other child API calls in APR: http://apr.apache.org/docs/apr/1.4/group__apr__thread__proc.html#gaf8d2be452a819161aa4cd6205a17761e then when a shutdown or restart occurs they get a hard 3 seconds to shutdown or they will be killed with SIGKILL. Up to that 3 seconds they will be sent a normal SIGTERM each second to try and get them to exit. Thus there is no facility to allow them to linger longer that I know of unless something has been added in more recent times. Graham On 26 December 2014 at 16:57, Stefan Priebe - Profihost AG < s.priebe@profihost.ag> wrote: > Hi list, > > i like mod fcgid a lot but there's one bug which makes me crazy. > > On DSO unload (Apache reload ) all child's get killed no matter if they > process requests or not. This makes no sense to me httpd processes itself > are also kept until all requests are served. > > Stefan > > Excuse my typo sent from my mobile phone. > --001a11c120a45e6d09050b184e40 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Sounds like it would perhaps be for the same reason as mod= _wsgi has issues with that sort of thing.

Only Apache ch= ild worker processes get special dispensation as far as graceful shutdowns = or reloads are concerned. If instead a module creates additional processes = using the other child API calls in APR:


<= /div>
then when a shutdown or restart occurs they get a hard 3 seconds = to shutdown or they will be killed with SIGKILL. Up to that 3 seconds they = will be sent a normal SIGTERM each second to try and get them to exit.

Thus there is no facility to allow them to linger long= er that I know of unless something has been added in more recent times.

Graham


On 26 December 2014 at 16:57, Stefan = Priebe - Profihost AG <s.priebe@profihost.ag> wrote:
=
Hi list,

i li= ke mod fcgid a lot but there's one bug which makes me crazy.
=
On DSO unload (Apache reload ) all child's get killed no= matter if they process requests or not. This makes no sense to me httpd pr= ocesses itself are also kept until all requests are served.

S= tefan

Excuse my typo sent= from my mobile phone.

--001a11c120a45e6d09050b184e40--