|
|
Posted by Jerry Stuckle on 07/28/07 01:21
davidkruger@techie.com wrote:
> On Jul 27, 3:17 pm, Jerry Stuckle <jstuck...@attglobal.net> wrote:
>> davidkru...@techie.com wrote:
>>> On Jul 27, 12:00 pm, Hans Fredrik Nordhaug <han...@gmail.com> wrote:
>>>> I'm trying to write to a file in the current directory - no remote
>>>> files. The subject says it all - I can add that both the directory
>>>> and the file is wordwritable. This happens on a (quite good) free
>>>> hoster in Norway which doesn't use safe mode, running PHP 5.1.6 as the
>>>> PHP info below shows ...
>>>> Test it at:http://home.no.net/moldevbk/fopen-test/?mode=w(write- fails)http://home.no.net/moldevbk/fopen-test/?mode=a(append- ok)http://home.no.net/moldevbk/fopen-test/p.php-PHP infohttp://home.no.net/moldevbk/fopen-test/fopen-test.phps-source code of test script.
>>>> I have searched the web and usenet, but not found this problem
>>>> mentioned before. I do realize that I can work around the problem by
>>>> truncating the file first and then appending to the empty file - but
>>>> that is ugly as ...
>>>> Regards, Hans
>>>> --
>>>> + It's GNU/Linux, not Linux ->http://www.gnu.org/gnu/linux-and-gnu.html
>>>> + Support the Free Software Foundation ->http://member.fsf.org/
>>>> + Become an Open Directory Project Editor ->http://dmoz.org/
>>> make sure the directory is set to allow group writing with permissions
>>> set to 707. then it shoudl allow it to work.
>> 707 is NOT a good one to use. It means anyone can write to the file.
>> And if it's not an executable file, you shouldn't have the execute bit on.
>>
>> 600 is great if the webserver is going to be the only one accessing it;
>> Otherwise you should use 660 with the proper group settings.
>>
>> --
>> ==================
>> Remove the "x" from my email address
>> Jerry Stuckle
>> JDS Computer Training Corp.
>> jstuck...@attglobal.net
>> ==================- Hide quoted text -
>>
>> - Show quoted text -
>
> You are right 707 wouldn't be a good one to use on a production
> server, but for testing purposes i think would be OK. I am thinking
> that the problem is when the script runs it is setup with a group of
> nobody, setting to 707 would allow that to write the file, if it were
> a permission problem causing the issue, using 707 would make anyone
> able to write to the folder, but would also tell for sure if the
> folder permissions are the cause of the problems the OP is having.
>
I would NEVER set anything up on a test server different than a
production server.
The purpose of a test server is to find problems BEFORE they occur. And
to do so, you need to emulate the production environment.
Setting different flags does NOT do this.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|