On Mon, Nov 12, 2012 at 09:08:59AM -0700, Scott Dowdle wrote:
I ran into a similar problem on a new Fedora 18 build host... and it
ended
up being that I didn't have selinux set to permissive mode. Check that and
if so, I'm guessing it will fix your problem.
Ooh. Could you file bugs against SELinux policy for this?
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>