Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Subject: child init/ exit and the apr_cleanup_register
From: michaelr <mypop@freenet.de>
To: modules-dev@httpd.apache.org
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 22 Nov 2011 09:19:45 +0100
Message-ID: <1321949985.6470.3.camel@radzewitz.freenet-ag.de>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

Hello again,

maybe another stupid question but i could not found any
example in the modules dir of the httpd source.

Let's say i have an child_init_function which opens a 
filehandle. This filehandle should be open until the child
ends.

In mod_example.c they register an cleanup function to call a
function on child exit.

static apr_status_t child_exit ( void *data )
	{
	//close file handle...

	return OK;
	}

static void child_init ( apr_pool_t *p, server_rec *s )
	{
	//open file handle...

	apr_pool_cleanup_register(p, s, NULL, child_exit) ;
	}

I understand the cleanup as a function which runs on pool_cleanup.
This could happend on any time which i can't control - right?

When i return an HTTP_INTERNAL_SERVER_ERROR in my handler function
as an example the cleanup get's called also but the child is still
alive. The filehandle is closed and on the next request i run into
some kind of trouble.

Is there a way to define a 'real' exit function or can i force child
shutdown in above example? What's the right way to do it correctly?

Thanks a lot and greetings
 Michael