search for: message1323968

...For > > complete SELinux messages. run sealert -l > > b7014747-0d8d-443e-8b9a-af868976452d > > ============================================= > > > <big output snip> Update: A bit of searching found a thread which pointed here: http://www.webservertalk.com/message1323968.html This is a talk about Bind 9.x on RHEL4, but I think it applies to C5 as well as the issue is SELinux and chrooted BIND implementations. Problem is, I'm still not sure what should be done. I'd rather not disable SELinux protection by doing this: setsebool -P named_disable_trans=1...

Hi all, On my newly up-and-running nameserver (CentOS 5), I noticed the following alerts in /var/log/messages after restarting BIND. (lines inserted to aid in reading). As I'm new to SELinux, I'm hoping for some pointers on 1) if this is an issue which simply *must* be addressed, or if it's something I should live with, and 2) how to eliminate the warming messages without sacrificing