From dev-return-10454-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Fri Oct 03 19:52:32 2003 Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 5576 invoked from network); 3 Oct 2003 19:52:32 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 3 Oct 2003 19:52:32 -0000 Received: (qmail 11861 invoked by uid 500); 3 Oct 2003 19:52:15 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 11557 invoked by uid 500); 3 Oct 2003 19:52:12 -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 11489 invoked from network); 3 Oct 2003 19:52:11 -0000 Date: Fri, 3 Oct 2003 20:52:14 +0100 From: Joe Orton To: dev@httpd.apache.org Cc: dev@apr.apache.org Subject: Re: Apache won't start - shared memory problem Message-ID: <20031003195214.GA9206@redhat.com> Mail-Followup-To: dev@httpd.apache.org, dev@apr.apache.org References: <3F7B00D8.2080402@sharp.fm> <3F7B039E.30000@sharp.fm> <3F7BC378.1090402@ubizen.com> <3F7DA814.6000602@sharp.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F7DA814.6000602@sharp.fm> User-Agent: Mutt/1.4.1i X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Fri, Oct 03, 2003 at 06:47:16PM +0200, Graham Leggett wrote: > Kris Verbeeck wrote: > > >That won't solve the problem, the shared memory segment is still registered > >somewhere in the kernel. I've had lots of problems with this too and only > >deleting the file does not solve it. You have to remove the segments from > >the kernel table too (see mail from Paul). > > Is there no way that some cleanup process (whether it involves deleting > a file, or talking to the kernel, doesn't matter) can be done before an > attempt is made to create the shared memory segment? The issue is that APR creates the shmem segments using O_EXCL or IPC_EXCL etc. I think I've come to the conclusion that this should just be fixed in APR, MM does an unlink/shm_unlink on the filename first, and that doesn't cause any headaches I know of. joe