Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@locus.apache.org Received: (qmail 60714 invoked from network); 25 May 2007 20:11:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 May 2007 20:11:30 -0000 Received: (qmail 2881 invoked by uid 500); 25 May 2007 20:11:34 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 2849 invoked by uid 500); 25 May 2007 20:11:34 -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 2840 invoked by uid 99); 25 May 2007 20:11:34 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 May 2007 13:11:34 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of djwortham@gmail.com designates 64.233.162.233 as permitted sender) Received: from [64.233.162.233] (HELO nz-out-0506.google.com) (64.233.162.233) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 May 2007 13:11:27 -0700 Received: by nz-out-0506.google.com with SMTP id v1so879174nzb for ; Fri, 25 May 2007 13:11:06 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=sA6ujcQYCvzRVRZ/1k5JmBvUIleP+sDYOyNlCSQ2x5DsjcjIlvshNihZoasRyGsQRxA0KL4skN6drHPnK8/qnc1D1EXtptaJ/h9+eikQcF5h23miwrO2oSVQfmsEC4vz4qOM6ZzOharySVn/cAZ1KI+tzhw0291vl3QoF5Q/E8c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=gz8q4g93EOKWJVJb5FLm1kIv1SwBygxKUpykFfvHRnxqiETVeoZcZESurjFAf+V++jdM8uIf2kwsMDGUj4WgIXaHlFqfUtDH5iQGgbdbcFnakAZCiutFW/Iqci008JHPouYutgBgERp4KrIEE/1SuNphr9VBPXrX/k0gJ1b+I9A= Received: by 10.114.132.5 with SMTP id f5mr1624069wad.1180123866222; Fri, 25 May 2007 13:11:06 -0700 (PDT) Received: by 10.115.90.13 with HTTP; Fri, 25 May 2007 13:11:06 -0700 (PDT) Message-ID: <5280fae50705251311u49613a58wa78e4050e82bb10f@mail.gmail.com> Date: Fri, 25 May 2007 13:11:06 -0700 From: "David Wortham" To: modules-dev@httpd.apache.org Subject: Re: Creating shm segment in module creation function In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_179636_22869286.1180123866171" References: X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_179636_22869286.1180123866171 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline C=E9sar, I would think the most important part of timing when you create the shm is that you time it so all of the child processes can attach to it. That means that at least the attachment calls have to be made after the parent process has created the child processes. You can probably do the majority of the setup while you are still in the parent process (which I assume is running during the module config creation phase). One other consideration you might have to take into account: if Apache starts up as root then switches to a less-priveleged user, the other user would still have to have access to the path and file of the shm (assuming it's not an anonymous shm) then you would run into problems creating the sh= m then trying to get the children to read/write it. Dave On 5/25/07, C=E9sar Leonardo Blum Silveira wrote: > > Hello all, > > Is there any problem if I try to create a shared memory segment in the > module config creation phase, instead of the post config phase? > > Thank you, > > -- > C=E9sar L. B. Silveira > http://cesarbs.wordpress.com/ > ------=_Part_179636_22869286.1180123866171--