Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@minotaur.apache.org Received: (qmail 68671 invoked from network); 12 Apr 2011 14:52:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Apr 2011 14:52:48 -0000 Received: (qmail 59085 invoked by uid 500); 12 Apr 2011 14:52:48 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 59054 invoked by uid 500); 12 Apr 2011 14:52:48 -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 59046 invoked by uid 99); 12 Apr 2011 14:52:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Apr 2011 14:52:48 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rs@bytecamp.net designates 212.204.60.9 as permitted sender) Received: from [212.204.60.9] (HELO mail.bytecamp.net) (212.204.60.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Apr 2011 14:52:41 +0000 Received: (qmail 83037 invoked by uid 89); 12 Apr 2011 16:52:20 +0200 Received: from stella.bytecamp.net (HELO ?212.204.60.37?) (rs%bytecamp.net@212.204.60.37) by mail.bytecamp.net with CAMELLIA256-SHA encrypted SMTP; 12 Apr 2011 16:52:20 +0200 Message-ID: <4DA46724.2050105@bytecamp.net> Date: Tue, 12 Apr 2011 16:52:20 +0200 From: Robert Schulze Organization: bytecamp GmbH User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8 MIME-Version: 1.0 To: modules-dev@httpd.apache.org Subject: Re: APR Shared Memory Usage References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, Am 12.04.2011 16:45, schrieb Brad.Goodman@schange.com: > > So - if I follow other examples - if I were to create the shared memory > segment > in a ap_hook_post_config hook function, it would be assured to be set-up > before > any child processes are forked, and inherited by them? see mod_shm_counter for a good example: http://www.codemass.com/mod_shm_counter/downloads/mod_shm_counter.c with kind regards, Robert Schulze