Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of sorinm@gmail.com designates
 209.85.216.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=fyfg6jFBLSkabH7RLcOjLmOg0J02Q4vnWSh1PIZLy9tEG5G0c5ldU7q6x8mxrspm44
         AljG38tSev5nj6RWi7uXXOFA04EDTM8S0PPjacg20SjHoBQq+6RJR++cGNVwVMnrxgSD
         BllFhblT0xBaUKpb4Zi3A3A9HYiXLralNnv74=
MIME-Version: 1.0
In-Reply-To: <BANLkTikgADEa-zwn-BCRQ8d7QDNmMe2Y4g@mail.gmail.com>
References: <BANLkTinTmZzceEDzT3+9N_0MHmdAA8FrWA@mail.gmail.com>
	<4330EAB7-1E2D-44C8-B8B6-9312843B03FC@inmon.com>
	<BANLkTikgADEa-zwn-BCRQ8d7QDNmMe2Y4g@mail.gmail.com>
Date: Mon, 20 Jun 2011 23:56:57 +0200
Message-ID: <BANLkTimRDyt_1H936oh=Q5vPp1LX4D_MFQ@mail.gmail.com>
Subject: Re: Module External Configuration
From: Sorin Manolache <sorinm@gmail.com>
To: modules-dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 20, 2011 at 22:46, Jason Funk <jasonlfunk@gmail.com> wrote:
> I have moved my configuration over to shared memory (following
> mod_shm_counter as an example) and it conceptually seems to be working. I=
 am
> storing a struct in the memory and members that share it's memory (such a=
s
> the last mod time of the configuration file) persist over multiple childr=
en.
> However, when I am loading the configuration file I have to allocate
> additional memory. This apparently doesn't get stored in the same shared
> memory as it isn't sticking around. How do I dynamically allocate new mem=
ory
> to the struct that lives in shared memory?

Try C++ and boost::interprocess::managed_shared_memory and
boost::interprocess::allocator.

Sorin

>
> Jason
>
> On Mon, Jun 20, 2011 at 3:29 PM, Neil McKee <neil.mckee@inmon.com> wrote:
>
>> In the mod-sflow implementation I have one thread responsible for readin=
g
>> in new configuration as it changes and writing it to a shared-memory are=
a
>> where the worker-processes/threads can pick it up whenever it changes. =
=A0 I
>> don't know if that is the best way or not, =A0but it's one data point fo=
r you.
>> =A0 Source code is here:
>>
>> http://mod-sflow.googlecode.com
>>
>> Neil
>>
>>
>> On Jun 20, 2011, at 11:39 AM, Jason Funk wrote:
>>
>> > Hello,
>> >
>> > The module that I am writing has an external configuration file that i=
t
>> > parses and loads into configuration when the server loads. Before ever=
y
>> > request it checks to see if the configuration file has been updated an=
d
>> if
>> > it has it reloads the configuration. The configuration should be share=
d
>> over
>> > the entire server. The problem I am running into is that after the
>> > configuration file is updated the new configuration gets reloaded and
>> stored
>> > in memory but after a little while, the configuration reverts back to
>> it's
>> > previous version. I assume that this is because a new process was spaw=
ned
>> to
>> > handle a new request and the updated memory didn't get carried over (e=
ven
>> > though the pointer address didn't change...)
>> >
>> > My question is this: What mechanism should I be using in order to
>> > store persistent, mutable, configuration data that is shared between
>> every
>> > child process?
>> >
>> >
>> > Jason
>>
>>
>