[phpa] Re: help....
- From: "Rich Foreman" <rich.foreman@xxxxxxxxxxxxxxxxxxxx>
- To: <phpa@xxxxxxxxxxxxx>
- Date: Mon, 18 Mar 2002 14:16:20 -0600
OK. I got that error fixed, BUT there are still no files being cached.
What could cause that? All of my php-accelerator settings are in a previous
email. Except, I just changed the memory to 4 Megs instead of 8 just to see
if that was the problem.
Thanks,
Rich Foreman
Network Manager
The Venture Group
rich.foreman@xxxxxxxxxxxxxxxxxxxx
-----Original Message-----
From: Nick Lindridge [mailto:nick@xxxxxxxxxxxxxxxxxxxxx]
Sent: Monday, March 18, 2002 2:08 PM
To: phpa@xxxxxxxxxxxxx
Subject: [phpa] Re: help....
> BUT, I just looked at error log again and it is FULL of this:
>
> [Mon Mar 18 11:11:22 2002] [warn] Cache open failed (pid 24814)
This means that phpa was unable to create and open a cache file. The cache
by default is /tmp, and needs to be writable by whatever used you're running
apache as. Normally that shouldn't be a problem because /tmp should be
writable by everyone, assuming that it isn't full. If you're using a
different cache dir, check that it's writable by everyone, or change the
owner to the user that apache is running as (as set in the httpd.conf file).
nick
------------------------------------------------------------------------
www.php-accelerator.co.uk Home of the free PHP Accelerator
To post, send email to phpa@xxxxxxxxxxxxx
To unsubscribe, email phpa-request@xxxxxxxxxxxxx with subject unsubscribe
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.338 / Virus Database: 189 - Release Date: 3/14/2002
-- Binary/unsupported file stripped by Ecartis --
-- Type: text/x-vcard
-- File: Rich Foreman (rich.foreman@xxxxxxxxxxxxxxxxxxxx).vcf
-- Desc: Rich Foreman (rich.foreman@xxxxxxxxxxxxxxxxxxxx).vcf
------------------------------------------------------------------------
www.php-accelerator.co.uk Home of the free PHP Accelerator
To post, send email to phpa@xxxxxxxxxxxxx
To unsubscribe, email phpa-request@xxxxxxxxxxxxx with subject unsubscribe
Other related posts: