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 jasonlfunk@gmail.com
 designates 209.85.161.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=afIGqqJo35gnRo4p1j1k6JwGf7Ylvpxdt5TEsWRZILcTKEt2BZ8rpw53L6vq8y5fU1
         zFQCY4YJt/wruP3DjlLXBUxF245lU6Y9mcdk64SbrOyUi6yqd+zq6Z0q2pA8fXSAT0Ul
         5WRVnQOzDam5tKDDyYB8OZlXBcbLwGiML/OZg=
MIME-Version: 1.0
In-Reply-To: <4330EAB7-1E2D-44C8-B8B6-9312843B03FC@inmon.com>
References: <BANLkTinTmZzceEDzT3+9N_0MHmdAA8FrWA@mail.gmail.com>
 <4330EAB7-1E2D-44C8-B8B6-9312843B03FC@inmon.com>
From: Jason Funk <jasonlfunk@gmail.com>
Date: Mon, 20 Jun 2011 15:46:57 -0500
Message-ID: <BANLkTikgADEa-zwn-BCRQ8d7QDNmMe2Y4g@mail.gmail.com>
Subject: Re: Module External Configuration
To: modules-dev@httpd.apache.org
Content-Type: multipart/alternative; boundary=00151747885c41c1a204a62ad7e8

--00151747885c41c1a204a62ad7e8
Content-Type: text/plain; charset=ISO-8859-1

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 as
the last mod time of the configuration file) persist over multiple children.
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 memory
to the struct that lives in shared memory?

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 reading
> in new configuration as it changes and writing it to a shared-memory area
> where the worker-processes/threads can pick it up whenever it changes.   I
> don't know if that is the best way or not,  but it's one data point for you.
>   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 it
> > parses and loads into configuration when the server loads. Before every
> > request it checks to see if the configuration file has been updated and
> if
> > it has it reloads the configuration. The configuration should be shared
> 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 spawned
> to
> > handle a new request and the updated memory didn't get carried over (even
> > 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
>
>

--00151747885c41c1a204a62ad7e8--