[systemd-devel] Expected behavior when systemd cannot load SELinux policy

Jan Synáček jsynacek at redhat.com
Fri Nov 7 02:30:44 PST 2014


Hello,

currently, when SELINUX=enforcing and SELINUXTYPE=<invalid value> are
set in /etc/selinux/config, systemd refuses to boot with
"Failed to load SELinux policy. Freezing."

Is this really what should happen? If SELINUX is set to permissive or
disabled, though, systemd happily continues booting. I think that that's
what should happen when SELINUX is set to enforcing as well. Plus a big
warning in the log, or maybe even on the console, of course.

What do you think?

Cheers,
-- 
Jan Synacek
Software Engineer, Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20141107/c37ec3f4/attachment.sig>


More information about the systemd-devel mailing list