Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Thu, 7 Feb 2002 09:46:36 -0800
From: Aaron Bannert <aaron@clove.org>
To: dev@httpd.apache.org
Subject: Re: configure option to specify mmap/shm
Message-ID: <20020207094636.H31582@clove.org>
Mail-Followup-To: Aaron Bannert <aaron@clove.org>, dev@httpd.apache.org
References: <A5374D237E78D41195810090279CC91A05603048@xcup04.cup.hp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A5374D237E78D41195810090279CC91A05603048@xcup04.cup.hp.com>
User-Agent: Mutt/1.3.23i

On Thu, Feb 07, 2002 at 09:21:20AM -0800, MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote:
> Nope.. It does not work (for me).. That's the reason I need to change to to
> use SHMGET_ANON.. I was thinking that there'a already a option available to
> do such things..
> 
> BTW, is it not strange that it picks up APR_USE_SHMEM_SHMGET, but not
> APR_USE_SHMEM_SHMGET_ANON and rather decides to select
> APR_USE_SHMEM_MMAP_ZERO.. 

For anonymous shared memory, it prefers MMAP_ZERO over SHMGET_ANON.
You probably have these on your system:
header:sys/mman.h
func:mmap()
func:munmap()
file:/dev/zero

Is there anything else we could test to see if it's not working? Is it
possible that MMAP_ZERO's implementation is simple broken? Send me
the error you are seeing, and optionally a truss output also.

-aaron