On Friday 15 September 2006 04:47, [EMAIL PROTECTED] wrote: > For example, I must set the permission as '755' or will get '/tftpboot: > Permission denied' error.
This does not make sense. SE Linux hooks are called after the traditional unix permission checks. So, opening the perms should not affect SE Linux at all. If SE Linux was involved, you will get avc messages. Did you get any? "ausearch -m avc -f tftpboot". > But in my environment, the permission of /tftpboot be mandated as '110'. So > by now, I have to stop the selinux protecting by setsebool. Is this a bug? There could be policy bugs, but we have to go through the normal troubleshooting steps of looking for the avc messages. Also, the quick way to find out if SE Linux is causing the problem is not to change the unix perms, but to run "setenforce 0" (you can put it back by "setenforce 1" after testing). Directory perms have nothing to do with SE Linux. -Steve _______________________________________________ rhelv5-beta-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-beta-list
