Somebody in the thread at some point said: >> SELinux doesn't care about file paths. If the directories have the right >> context labels, it doesn't matter where they are. > > You need more than the directories to be right. Sometimes the files inside the > /var is hardcoded. It doesn't consider file paths when examining what it was you wanted to touch to see if you can. But when you create a file, by cp or whatever, it must use private knowledge about the specific path's "natural" context or it can't automagically label new files correctly based on where they were created. Maybe it will be possible to adjust the policies to accept both /var/blah and /srv/blah, or via a bool. -Andy -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
