Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of info@bnoordhuis.nl designates
 209.85.161.173 as permitted sender)
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:01:55 +0200
Message-ID: <BANLkTim3kbyCcvR2nNK90Yr_F98jvzxW=A@mail.gmail.com>
Subject: Re: Module External Configuration
From: Ben Noordhuis <info@bnoordhuis.nl>
To: modules-dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1

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 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?

You cannot (portably), you'll have to reserve the extra space when you
the allocate the shared memory.