<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 10/03/12 05:59, Chris Robinson wrote:
<blockquote
cite="mid:1331323193.83321.YahooMailNeo@web114702.mail.gq1.yahoo.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=iso-8859-1">
<div>
<div><span>"... file does not exist" when it obviously does
sounds like a permissions problem. I haven't done it so
haven't got the magic bullet for you, but review how
permissions and groups need to be set up for php. I seem to
recall (from my reading) that there's a simple but quite
counter intuitive need to set groups or permissions, or
something.</span></div>
</div>
</blockquote>
<br>
There aren't usually any special user/group permissions for PHP that
are different to Apache (i usually have all of my files owned by
root with group www-data, and only make certain files/dirs group
writable), but i think Chris is on the right track. Check each
component of the path all the way down. Here's a quick little shell
function to do it:<br>
<br>
lspath() {<br>
local dir="$1"<br>
while [ "$dir" != "/" ]; do<br>
echo "$dir"<br>
dir=$(dirname "$dir")<br>
done | xargs -d'\n' ls -ld<br>
}<br>
<br>
One stupid mistake i've made before is misreading the head portion:
e.g. /srv/www is the preferred location for web pages on newer
installs, but because /var/www was used for so long, i overlook the
difference between /var & /srv until i realise that i'm working
in completely the wrong tree.<br>
<br>
Paul<br>
</body>
</html>