On Thu, 2001-12-06 at 10:59, Ryan Bloom wrote:
>
> This took me a while to track down, but I did it. One of the engineers at
> Covalent tried to start Apache with a full /tmp file system. None of his
> Apache
> directives pointed to /tmp, so he assumed he would be okay. Unfortunately,
> he wasn't, the server was giving him an error because /tmp was full.
>
> The problem is that apr_initialize() calls apr_pool_init(), which creates a
> lock file in /tmp/aprXXXXXX. I think apr_initialize should take a path to
> create the lock file in. That would allow Apache to provide the correct path.
>
> The biggest problem is that this would change the API for the one function
> that must be in every APR program.
>
> Thoughts?
I don't think it would be worth the time and effort.
running with a full /tmp is not very healthy for the system at all.
maybe a better error message in apr_initialize saying 'unable to create
lockfile /tmp/aprXXXX
is all that is needed?
>
> Ryan
> ______________________________________________________________
> Ryan Bloom [EMAIL PROTECTED]
> Covalent Technologies [EMAIL PROTECTED]
> --------------------------------------------------------------
--
Ian Holsman [EMAIL PROTECTED]
Performance Measurement & Analysis
CNET Networks - (415) 344-2608
