On Mon, Nov 03, 2014 at 09:59:26AM -0500, JCURREY at aol.com wrote: > > Turned out to be selinux. I hope you figured out what was wrong with the SELinux attributes on the files. Turning off SELinux and calling it fixed isn't really a solution. -- Jonathan Billings <billings at negate.org>