Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 94812 invoked by uid 500); 3 Nov 2002 03:26:11 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 94793 invoked from network); 3 Nov 2002 03:26:10 -0000 Subject: Re: Pool common to all processes/threads From: Bojan Smojver To: Apache Dev List In-Reply-To: <5.1.0.14.2.20021101000921.031f8728@pop3.rowe-clan.net> References: <5.1.0.14.2.20021101000921.031f8728@pop3.rowe-clan.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 03 Nov 2002 14:27:07 +1100 Message-Id: <1036294027.1205.18.camel@beast.rexursive.com> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Thanks Brian and Bill. Bojan On Fri, 2002-11-01 at 17:11, William A. Rowe, Jr. wrote: > At 11:48 PM 10/31/2002, Bojan Smojver wrote: > >Just reading through the documentation to find if there is a single pool that > >all processes/threads have access to, without mucking around with direct shared memory allocation. So far, couldn't fine one in Apache 2. Does it exist? > > If you are looking for config-time write, later read-only, use the process pool > you can find from the server rec. You must set it up early, you can't modify > stuff in it later. > > If you want full blown read-write access, you must create your own apr_shm. > You can wrap that in an apr_rmm, if you want malloc/realloc/free behavior > in that shared memory block. Thanks. Bojan