-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/06/2011 02:51 PM, Joe Zeff wrote: > On 06/06/2011 08:07 AM, Daniel J Walsh wrote: >> Please do not suggest to turn SELinux off at boot everytime something >> goes wrong on a Fedora System. As root you can turn SELinux into >> permissive mode. setenforce 0, then try your application, if it works >> then SELinux is probably the problem, if it fails SELinux is not the >> problem and you can turn SELinux enforcement back on. setenforce 1. >> Your method will cause a relabel when SELinux is turned back on. > > Not only that, if you have the SELinux Troubleshooter working (and you > should, you know) it will pop an alert if and when there's a problem > with SELinux. I have BOINC running and one of the projects is > Einstein@home. For some reason, SELinux doesn't understand that all of > the Einstein projects need to have access to certain device files and it > keeps complaining. Granted, the projects are run in permissive mode so > that the access isn't blocked, but it's a tad monotonous to have to > reset the context for almost every project I do. (There doesn't seem to > be an overall fix for this because it's filename specific.) If you're > not getting any alerts, there's almost no chance that SELinux is involved. Joe can you send me an example of the AVC you are seeing? Is this F15? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAk3tInYACgkQrlYvE4MpobOOFACggeb72oVcslfc5JK4/tCMulWA q6kAnRK4E2FspAZvVxDkTbn23zzszSzG =u95g -----END PGP SIGNATURE----- -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
