On Dec 31, 2013, at 8:57 AM, Daniel J Walsh dwalsh@redhat.com wrote:
THere was a bug in libselinux which is now fixed, that was causing the problem.
Right, but I thought that the bug caused the setting in /etc/selinux/config being ignored, while selinux=0 and enforcing=0 still worked?
Chris Murphy