Mac Os 10 +

[tristan]

Recently ive been migrating a PHP4 application build on a fedora Linux,
to a MacOs10+ with PHP5.

The most significant problem i have been experiencing is file based
functions specifically functions handleing directories.

For example both is_executable(), openDir() are returning false when
the directories are setup and premissions are correct. I can access
files in a directory but not execute functions on a directoy itself.

For instance file_get_contents("/images/1.jpg") will work fine. However
openDir("/images/") will fail.

Has anyone else experienced the same sort of problem, if so did you
find a fix or workaround?

- Tristan

[NC]

tr*****@med.usyd.edu.au wrote:

Recently ive been migrating a PHP4 application build on a fedora
Linux, to a MacOs10+ with PHP5.
First of all, it pays to remember that MacOS X, when it comes to the
inner workings of the file system, is nothing but a BSD Unix. The "X"
conveniently has two meanings; it's the 10th major release of MacOS,
which also happens to be an X-Window GUI...
For example both is_executable(), openDir() are returning false when
the directories are setup and premissions are correct. I can access
files in a directory but not execute functions on a directoy itself.
In Unix (and, hence, in MacOS X), opening a directory and reading its
contents are operations that require execute privileges. Reading a
file is an operation that requires read privileges. If PHP does not
have execute privileges, this is exactly what you should expect to
happen.
For instance file_get_contents("/images/1.jpg") will work fine.
However openDir("/images/") will fail.

Give PHP execute rights on the directory in question...

Cheers,
NC

[tristan]

Well thats the confusion and the first thing we looked at. The
directories do have full execute permissions.

So far we have looked at the php permissions for users + groups enabled
execution on the relevant directories without success.

I'm sure there is something obvious which we are missing..

[d]

"NC" <[e-mail]> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...

tr*****@med.usyd.edu.au wrote:

Recently ive been migrating a PHP4 application build on a fedora
Linux, to a MacOs10+ with PHP5.

First of all, it pays to remember that MacOS X, when it comes to the
inner workings of the file system, is nothing but a BSD Unix. The "X"
conveniently has two meanings; it's the 10th major release of MacOS,
which also happens to be an X-Window GUI...

Not by default it isn't :)

[Jasen Betts]

On 2006-02-15, tr*****@med.usyd.edu.au <tr*****@med.usyd.edu.au> wrote:

Recently ive been migrating a PHP4 application build on a fedora Linux,
to a MacOs10+ with PHP5.

The most significant problem i have been experiencing is file based
functions specifically functions handleing directories.

For example both is_executable(), openDir() are returning false when
the directories are setup and premissions are correct. I can access
files in a directory but not execute functions on a directoy itself.

For instance file_get_contents("/images/1.jpg") will work fine. However
openDir("/images/") will fail.

Has anyone else experienced the same sort of problem, if so did you
find a fix or workaround?

sounds like you don't have execute permission for the directory.
can you check that?

--

Bye.
Jasen

[tristan]

Its an interesting situation and we've tried the following combinations
of users, groups with x permission.

human user = A
human user group = AG
apache user = B
Apache user Group = BG
Independate Group = IG
rwx A AG
rwx B AG
rwx A BG
rwx B BG

Setting both A and B to be members of IG
rwx A IG
rwx B IG

We have also looked at the heirachy of the directories, incase there
was a setting cascading down which may have affected it, and issues
such as wether Apache was configured not to allow directory listings
just of the off chance it may affect it, wether there was something
changed in the implimentation of file and directory handling in PHP5 vs
PHP4, and is there anything particular about the Mac systems that we
might have missed which is where im at now.

Come to think of it, I did have a similar problem once before on a
Fedora box with a different application, the solution was to create an
independant group that mimicked the group that the software was under
on the original system. Though I never found out exactly why that
worked.
- Tristan

[Jasen Betts]

On 2006-02-15, tr*****@med.usyd.edu.au <tr*****@med.usyd.edu.au> wrote:

Well thats the confusion and the first thing we looked at. The
directories do have full execute permissions.

So far we have looked at the php permissions for users + groups enabled
execution on the relevant directories without success.

I'm sure there is something obvious which we are missing..

enable them for everyone, if that helps check the id that php is running
under

Bye.
Jasen