apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Pane <brian.p...@cnet.com>
Subject Re: Problem with memory initialization.
Date Thu, 06 Dec 2001 19:23:44 GMT
Ryan Bloom wrote:

>On Thursday 06 December 2001 11:11 am, Aaron Bannert wrote:
>
>>>The biggest problem is that this would change the API for the one
>>>function that must be in every APR program.
>>>
>>>Thoughts?
>>>
>>Is it the lock routine or something specific to apr_pool_init that is
>>creating the tmpfile? In general I think given the current state of
>>
>
>It is the apr_pool_init function, which is creating the lock with a NULL
>fname, so it is a bigger problem than just the pool lock.
>

Why is the pool initialization creating a crossprocess lock?!

--Brian


Mime
View raw message