Hmm - have you tried turning SELinux off completely and seeing if the problem persists?
I.e. on my FC6 system, in /etc/selinux/config:
Code:
SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - SELinux is fully disabled.
SELINUX=disabled
# SELINUXTYPE= type of policy in use. Possible values are:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
SELINUXTYPE=targeted
and then a reboot... then retry what you think is being broken by SELinux.
BTW. I think SELinux is way too overcomplicated and neurotic for general use in most non National Security Agency environments, and it imparts so many hurdles to configuring a working server / system that it is just not worth the effort. I find it difficult enough to get a simple web development (LAMP server) set up already, without SELinux inserting even more hurdles and configuration complexities.