From dev-return-8452-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Wed Nov 20 04:34:09 2002 Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 57417 invoked by uid 500); 20 Nov 2002 04:34:09 -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 57364 invoked from network); 20 Nov 2002 04:34:08 -0000 Date: Tue, 19 Nov 2002 20:33:28 -0800 Subject: Re: [PATCH] Re: apr_proc_mutex is broken Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v548) From: Aaron Bannert To: dev@apr.apache.org Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: <3791458A-FC41-11D6-8BFD-000393B3C494@clove.org> X-Mailer: Apple Mail (2.548) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tuesday, November 19, 2002, at 10:46 AM, wrote: > > If you don't want the child process to destroy the mutex, then you > should > kill that cleanup in the child process. That is why we have the > apr_pool_cleanup_kill API. > Naw, we just shouldn't automatically destroy locks in a cleanup. Destroying all mutexes should just become the responsibility of the application. -aaron