Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@minotaur.apache.org Received: (qmail 63058 invoked from network); 1 Jun 2010 09:48:05 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Jun 2010 09:48:05 -0000 Received: (qmail 57108 invoked by uid 500); 1 Jun 2010 09:48:05 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 56447 invoked by uid 500); 1 Jun 2010 09:48:02 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 56435 invoked by uid 99); 1 Jun 2010 09:48:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jun 2010 09:48:02 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [64.202.165.181] (HELO smtpauth01.prod.mesa1.secureserver.net) (64.202.165.181) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 01 Jun 2010 09:47:53 +0000 Received: (qmail 7414 invoked from network); 1 Jun 2010 09:47:30 -0000 Received: from unknown (76.252.112.72) by smtpauth01.prod.mesa1.secureserver.net (64.202.165.181) with ESMTP; 01 Jun 2010 09:47:30 -0000 Message-ID: <4C04D71E.7040204@rowe-clan.net> Date: Tue, 01 Jun 2010 04:47:10 -0500 From: "William A. Rowe Jr." User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 To: modules-dev@httpd.apache.org Subject: Re: Can an Apache module inject configuration in runtime? References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 6/1/2010 4:39 AM, Andrew Godziuk wrote: > > I'm wondering if it's possible for an Apache module to change global > config structures. If you don't do this during startup, beware. You are exploding memory by taking what were copy-on-write shadow pages of the original parent process, and munging X copies where X is the number of worker processes you have. And if it is threaded, outch.