CentOS - Oct 2006 - Directories not writable (Apache/PHP)

Hi,

I have a new CentOS sever install. I've also installed suPHP to
replicate a live server.

When I upload file via FTP the permissions seem OK, however the
directories copied are not writable?? Any ideas?

I have tried chmod 777 and that's not working either. Could is be a
suPHP issue?

I have 'suPHP_UserGroup GROUP USER' setup in my virtual directory and
the user is also in the users & groups. The suPHP log file shows the php
file executing OK.

Any ideas?

Thanks,
Mark.

Update to original issue:

There is error messages regarding this problem coming up on the main PC
screen:

--
Avc: denied [ write ] for pid=6890 com="php" name="temp"
dev=dm-0
ino=442565 scontext=user_u:system_r:httpd_t
tcontext=user_u:object_r:root_t tclass=dir
--
Plus lots more for all the directories and files my PHP script is trying
to write to.

Anyone know about this issue??

Thanks,
Mark.


-----Original Message-----
From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On
Behalf Of Mark Fitzsimmons
Sent: 09 October 2006 09:57
To: CentOS mailing list
Subject: [CentOS] Directories not writable (Apache/PHP)

Hi,

I have a new CentOS sever install. I've also installed suPHP to
replicate a live server.

When I upload file via FTP the permissions seem OK, however the
directories copied are not writable?? Any ideas?

I have tried chmod 777 and that's not working either. Could is be a
suPHP issue?

I have 'suPHP_UserGroup GROUP USER' setup in my virtual directory and
the user is also in the users & groups. The suPHP log file shows the php
file executing OK.

Any ideas?

Thanks,
Mark.


_______________________________________________
CentOS mailing list
CentOS at centos.org
http://lists.centos.org/mailman/listinfo/centos

>> --
>> Avc: denied [ write ] for pid=6890 com="php"
>> name="temp" dev=dm-0
>> ino=442565 scontext=user_u:system_r:httpd_t 
>> tcontext=user_u:object_r:root_t tclass=dir
>This error is related to SeLinux

Thanks DM, have disabled SeLinux and all is OK. I assume for a non live
testing server, disabling SeLinux would be OK?