Does anything special have to be done to cause SELinux to start using newly added local filecontexts? What I'm finding is that if I use semanage fcontext -a to add a local filecontext definition, it is not used by restorecon unless I specify the "-F" option. Without the "-F" option, restorecon -vv <file_path> gives the following message: /sbin/restorecon: <file_path> not reset customized by admin to <current_context> but restorecon -vv -F <file_path> gives this: /sbin/restorecon reset <file_path> context <current_context>-><new_context> I've also tried using /usr/sbin/semodule --build to try rebuilding (and reloading) the current policy, but that didn't change the behavior I'm seeing. Any suggestions would be greatly appreciated. - Tim -- View this message in context: http://www.nabble.com/Question-on-semanage-fcontext--a-tp15240526p16058319.html Sent from the Fedora SELinux List mailing list archive at Nabble.com. -- fedora-selinux-list mailing list fedora-selinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-selinux-list
