quantumburnz
13th October 2008, 11:42 PM
I ran the PreUpgrade from FC9 -> FC10 Beta, and now I get "Error starting client thread" when I try to run Folding@Home. I also get the following from dmesg when I try to run it:
type=1400 audit(1223922994.984:7): avc: denied { execmem } for pid=3920 comm="fah6" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=process
I temporarily disabled SELinux and F@H ran ok. I've found that if I go into SELinux Administration -> Boolean and check the global module for allow_execmem that F@H starts working. However, the description for the allow_execmem module says "Allow unconfined executables to map a memory region as both executable and writeable, this is dangerous and the executable should be reported in Bugzilla." So would this be something I should bring up with the SELinux Bugzilla, Fedora Bugzilla, etc? Any thoughts?
type=1400 audit(1223922994.984:7): avc: denied { execmem } for pid=3920 comm="fah6" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=process
I temporarily disabled SELinux and F@H ran ok. I've found that if I go into SELinux Administration -> Boolean and check the global module for allow_execmem that F@H starts working. However, the description for the allow_execmem module says "Allow unconfined executables to map a memory region as both executable and writeable, this is dangerous and the executable should be reported in Bugzilla." So would this be something I should bring up with the SELinux Bugzilla, Fedora Bugzilla, etc? Any thoughts?
