Just temporarily switch it off per: http://www.crypt.gen.nz/selinux/disable_selinux.html
and see if it makes a difference. I get in trouble here from people saying to completely disable it. Once determined that is issue then go through process of configuring SELinux so it allows access to that directory for Apache user. Graham On 31 March 2011 13:28, Fred <[email protected]> wrote: > Good call! I'm not a sysadmin and did not setup this system, but after > a quick google I found the file below. I'll talk to our sysadmin > tomorrow and see if this is an issue to change or he just got it by > default on a new system build. I'll also try disabling it and see if > that fixes the issue. > > /etc/selinux/config > > # This file controls the state of SELinux on the system. > # SELINUX= can take one of these three values: > # enforcing - SELinux security policy is enforced. > # permissive - SELinux prints warnings instead of enforcing. > # disabled - No SELinux policy is loaded. > SELINUX=enforcing > # SELINUXTYPE= can take one of these two values: > # targeted - Targeted processes are protected, > # mls - Multi Level Security protection. > SELINUXTYPE=targeted > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
