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.

> apr_file_mktemp and that we create cross-process locks that need tmp
> files, a full /tmp will still be a problem in other places in the app.
>
> Maybe apr_initialize could take a path to create all tmp files in
> (or was that what you were suggesting)?

It is the next logical step to what I was suggesting.  I will through 
something together today.

Ryan

______________________________________________________________
Ryan Bloom                              [EMAIL PROTECTED]
Covalent Technologies                   [EMAIL PROTECTED]
--------------------------------------------------------------

Reply via email to