From dev-return-8724-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Fri Dec 13 20:40:24 2002 Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 21076 invoked by uid 500); 13 Dec 2002 20:40:23 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 21065 invoked from network); 13 Dec 2002 20:40:23 -0000 Mime-Version: 1.0 X-Sender: jimpop@devsys.jagunet.com Message-Id: In-Reply-To: <20021213172057.GB30863@redhat.com> References: <20021213172057.GB30863@redhat.com> Date: Fri, 13 Dec 2002 15:40:20 -0500 To: Joe Orton , dev@apr.apache.org From: Jim Jagielski Subject: Re: [PATCH] apr_shm_create/shmget/fopen flags Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N At 5:20 PM +0000 12/13/02, Joe Orton wrote: >For the implementation of name-based apr_shm_create using shmget (i.e. >the filename != NULL case), I've got two questions: > >1) why is APR_EXCL passed to the apr_file_open call? This is annoying >for Apache since if the server crashes, you have to remove the shmem >segment *and* the filename before restarting. Patch below OK? > Basically, it's a protection mechanism. Since each segment is backed up with a file, you want (and need) to ensure that APR has sole access/control over that file, hence the EXCL setting. -- =========================================================================== Jim Jagielski [|] jim@jaguNET.com [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither" - T.Jefferson