Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 89075 invoked by uid 500); 13 Oct 2001 00:23:39 -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 89030 invoked from network); 13 Oct 2001 00:23:38 -0000 Date: Fri, 12 Oct 2001 17:23:44 -0700 (PDT) From: Dirk-Willem van Gulik X-X-Sender: dirkx@titatovenaar.sfo.covalent.net To: dev@httpd.apache.org, Subject: Re: mod_asis; apr_bucket_file_create->destroy->poolcleanup->fileclose In-Reply-To: <20011012231252.3C28746DFC@koj.rkbloom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, 12 Oct 2001, Ryan Bloom wrote: > The model is REALLY simple. apr_file_t's are created by apr_file_open, at > that time, a cleanup is registered on the pool that was passed into the file_open > function. apr_bucket_file_create just creates a bucket and puts the file into > it. When the bucket is destroyed, the bucket is freed() and we check the > refcount to determine if we should call apr_file_close. Hmm - I see it going to file_free(); but then not going to apr_file_close(). but I get the gist now - digging deeper. Dw