Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 89844 invoked by uid 500); 2 Jun 2002 21:52:32 -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 89827 invoked from network); 2 Jun 2002 21:52:32 -0000 Message-ID: <3CFA93A0.2020705@apache.org> Date: Sun, 02 Jun 2002 14:52:32 -0700 From: Ian Holsman User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0+) Gecko/20020519 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@httpd.apache.org Subject: apache under linux -- restarting problems Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I've just run into this, and it is present in 2.0.36.. the name-based sysvmem isn't appropiate as it will cause apache to refuse to start when you upgrade a module (forcing a reboot) a simple way to 'fix' is this it for the server to write out in the error message what sharedmem segment it is trying to create so you can ipcrm it. otherwise your forced to remove them all which is not a good thing