On Sat, 13 Aug 2011, Tim Dunphy wrote:

> actually i replied to the wrong thread. D'OH! But it seems that SELinux was 
> behind each problem..
>
> setenforce 0 on that machine allowed it to work. Tho I readily admit that I 
> wish I was more familiar with SELinux. :)

You can use audit2allow to create SELinux policy for whatever is not 
working.  I'd hate for you to disable SELinux altogether because of a few 
issues.

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

Reply via email to