From dev-return-5082-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Thu Dec 06 19:14:43 2001 Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 56576 invoked by uid 500); 6 Dec 2001 19:14:42 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 56565 invoked from network); 6 Dec 2001 19:14:42 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Ryan Bloom Reply-To: rbb@covalent.net Organization: Covalent Technologies To: Ian Holsman Subject: Re: Problem with memory initialization. Date: Thu, 6 Dec 2001 11:16:56 -0800 X-Mailer: KMail [version 1.3] Cc: dev@apr.apache.org References: <20011206185921.7541D46E02@koj.rkbloom.net> <1007665408.11110.52.camel@griffon.nasa.cnet.cnwk> In-Reply-To: <1007665408.11110.52.camel@griffon.nasa.cnet.cnwk> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20011206191656.D778546E02@koj.rkbloom.net> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thursday 06 December 2001 11:03 am, Ian Holsman wrote: > 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? The real problem is that now you have a lock file that isn't under the control of the administrator at all. I dislike that a lot. Ryan ______________________________________________________________ Ryan Bloom rbb@apache.org Covalent Technologies rbb@covalent.net --------------------------------------------------------------