I have an application I test at work, that has always failed installation on systems with SELinux enabled. Our published workaround involves issuing a chcon command for the library-file at the center of the failure.
chcon -t textrel_shlib_t /usr/lib/ourfile.so.1.0.20
In RHEL5, this has worked for us, and allows the application to function correctly, without having to completely disable SELinux.
Under RHEL6, the chcon command gives no errors, but we still see the same error, when our application is started as a daemon, via
My primary concern is figuring out an updated workaround (the application library in question is submitted to an external certification process, and can't be changed for another 6 months), but I'm also curious if this indicates an intentional change from RHEL5 to RHEL6.