José Ricardo wrote:
Problem solved.
It was in /etc/selinux/config, the option SELINUX=enforcing
I put disabled and it worked.
Gotta find if there isn't a more ellegant way to solve this.

there is, you gonna have to write a setup of rules for se-linux ;)
i hadn't time yet for this - may be some work and timeconsuming job

usal way to go: set selinux to Permissiv (means, checks rules and writes into log but does not enforce), take the logfile and use some of the tools, which may generate some rules out of the failed access, optimize them by hand until it works ;) - more help will be at the selinux lists and webpages i think...

there is a special list for selinux und federoa:
[EMAIL PROTECTED]

just in case you would like to have it running with selinux in enforcing mode... so if you get some rules to get it running, would be nice to share them


greetings
dalini

--
fingerprint :: F5E8 DAF5 3CD2 2B52 82A2  0AE7 36D5 B889 25E7 15C8
pub         :: 1024D/25E715C8 [expires: 2007-09-09]
sub         :: 2048g/4DE4FB70 [expires: 2007-09-09]



Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to