https://bugzilla.redhat.com/show_bug.cgi?id=1369954 I'm not sure what's caused this, I'm still trying to track it down. But enforcing=0 does work around it. It might be a recent selinux-policy of systemd update that's broken it. -- Chris Murphy -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
