<div dir="ltr">Hi,<div><br></div><div><div>~ getenforce </div><div>Enforcing</div></div><div><br></div><div>Please be aware that setenforce will only change the mode SELinux is running in. For a permanent change, you have to edit the configuration file.</div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jul 20, 2015 at 4:32 PM jd1008 <<a href="mailto:jd1008@gmail.com">jd1008@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On 07/20/2015 12:38 PM, Martin Cigorraga wrote:<br>
> Hi,<br>
><br>
> I created the file /.autorelabel (# touch /.autorelabel), set SELinux<br>
> to 'enforcing' and (/etc/sysconfig/selinux) and rebooted.<br>
><br>
> May be I could do it without rebooting as stated in this question:<br>
> <a href="https://serverfault.com/questions/453137/how-can-i-do-an-selinux-filesystem-relabel-without-rebooting-firstbut" rel="noreferrer" target="_blank">https://serverfault.com/questions/453137/how-can-i-do-an-selinux-filesystem-relabel-without-rebooting-firstbut</a><br>
> before landind there I was unaware of the 'fixfiles' tool :)<br>
><br>
> HTH, let us know if not.<br>
><br>
><br>
> On Mon, Jul 20, 2015 at 3:31 PM jd1008 <<a href="mailto:jd1008@gmail.com" target="_blank">jd1008@gmail.com</a><br>
> <mailto:<a href="mailto:jd1008@gmail.com" target="_blank">jd1008@gmail.com</a>>> wrote:<br>
><br>
><br>
><br>
> On 07/20/2015 12:23 PM, Martin Cigorraga wrote:<br>
> > Hello folks,<br>
> ><br>
> > It happened to me too that about a week or so ago SELinux<br>
> > automatically turned to 'Permissive' with an upgrade of<br>
> > selinux-related packages, I had to relabel everything to get things<br>
> > back to its previous state.<br>
> ><br>
> > Although I didn't delve in the issue at that moment I will keep<br>
> an eye<br>
> > on this issue should it happens again.<br>
> ><br>
> > Cheers,<br>
> > -Martín<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> So how did yo set it back to Enforcing?<br>
><br>
After I executed<br>
setenforce Enforcing<br>
touched /.autorelabel and rebooted,<br>
during the reboot, the labeling was taking place, and I saw<br>
3 messages, which I cannot see anywhere in /var/log.<br>
The messages included that plymouthd killed systemd<br>
and that some file or directory in /lib/modules/ had too many<br>
symlinks or some such, and the relabeling died at when it was at about 13%.<br>
<br>
--<br>
users mailing list<br>
<a href="mailto:users@lists.fedoraproject.org" target="_blank">users@lists.fedoraproject.org</a><br>
To unsubscribe or change subscription options:<br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/users" rel="noreferrer" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/users</a><br>
Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" rel="noreferrer" target="_blank">http://fedoraproject.org/code-of-conduct</a><br>
Guidelines: <a href="http://fedoraproject.org/wiki/Mailing_list_guidelines" rel="noreferrer" target="_blank">http://fedoraproject.org/wiki/Mailing_list_guidelines</a><br>
Have a question? Ask away: <a href="http://ask.fedoraproject.org" rel="noreferrer" target="_blank">http://ask.fedoraproject.org</a><br>
</blockquote></div>