On Tuesday, November 19, 2002, at 12:02 PM, Philip Martin wrote:
I think the current pool cleanup handler is a mistake. The handler should cleanup only those resources local to the process, leaving the proc_mutex in a working state.
This is how it is now, only that when we use fork(), all the cleanups in the parent are magically inherited in the children. We should simply just not register cleanups for mutexes, as you say here:
It should be the application's responsibility to call (or fail to call :) apr_proc_mutex_destroy at the appropriate place.
+1
-aaron
