Why doesn't chmod -R 777 works?

Snouser · 09-03-2008, 02:05 PM

I've a script that's suppose to change somethins in a folder.
The only problem is that the script don't 've writing wrtites to the folder.

Just to be clear.

First I've a .sh file thats start when the computer goes on. The script look like this.

Code:

while true; do
/var/www/script/script.php
sleep 60
done

It runs the script every 60 sec.
The script it self starts with this line:
#!/usr/bin/php5

Does this mean that the php5 binary runs the script?

The problem is that none of the scripts 've writing writes to the folder.

I've tried to chmod -R 777 on the folder, but it doesn't mater.

What rights should I give the folder?

CRC123 · 09-03-2008, 02:29 PM

Looks like you're trying to run shell code through the php interpreter which won't work.
Try replacing the #!/usr/bin/php5 with

Quote:

#!/usr/bin/sh
or
#!/usr/bin/bash

Also, why not use cron to run your script every 60 seconds?

Snouser · 09-03-2008, 02:46 PM

Thanks for the replay.

I just notest that when the user www-data (apache2) creates a folder, then the php5 binary can't write to it. So I've to manual run chmod -R 777 on the folder.

How do I change the rights so that php5 can write to a folder apache has created? Is it possible to add them to the same grope, how if so?

OffT: Why I don't use cron is because the cript doesn't take <60 sec to run so if I run is as cron more then one script will be running at the same time. With my solution it will wait 60 seconds after it's finish. Maybe there is a better way, but this works fine for now.

EDIT: The script I'm trying to run is written in php. So the top line should be correct. If I run the script as root in a terminal it works perfect.

bathory · 09-04-2008, 02:15 AM

Since it's a shell script it should start with

Code:

#!/bin/sh

or whatever your shell is.
Now to run the php script from inside the shell script you should use the php command:

Code:

php /var/www/script/script.php

You can su to www-data before running the command above, or you can chown/chmod the folder created.

Mr. C. · 09-04-2008, 03:04 AM

To solve permissions problems, you need to know:

1) the UID/GID of the process that wants access
2) the UID, GID, and permissions of the file/directory that (1) will be accessing

Please provide answers to (1) and (2).

jlliagre · 09-04-2008, 03:10 AM

Php being an interpreter like shells are and php accepting # as a comment character, I think it is valid to insert the following header to a php source file in order to have it being a php executable:

Code:

#!/usr/bin/php5

John VV · 09-04-2008, 03:43 AM

you Never,Never,never chmod -r 777 www-data (apache2) you just gave EVERY PERSON ON THE WEB FULL READ/WRIGHT/EXECUTE PERMISION to your server .

Mr. C. · 09-04-2008, 03:55 AM

Quote:

Originally Posted by John VV

you Never,Never,never chmod -r 777 www-data (apache2)you just gave EVERY PERSON ON THE WEB FULL READ/WRIGHT/EXECUTE PERMISION to your server .

And what permissions do you advise for web applications that upload data? Apache needs write permission for such activities.

Access controls are generally used at a higher layer, but the underlying file system permissions must be set such that the web server can write if writing is to be allowed..

John VV · 09-04-2008, 10:59 AM

chown -R apache:apache www-data
chmod -R 755 www-data

Mr. C. · 09-04-2008, 05:39 PM

John VV - since you've given apache ownership to the files/directories, you get exactly the behavior you said to avoid in post #7. Removing group write permission here serves no purpose with respect to apache, as it already owns the files so group ownership is unimportant. Removing access for Other users only prevents LOCAL users from making changes to the files.

Thus, your suggested permissions and ownership do not meet your stated criteria.