10 Aug
2007
10 Aug
'07
6:03 p.m.
On Fri, 2007-08-10 at 14:38 +0100, Shamim wrote:
Hi,
I found some work around for this issue.
in the "/etc/selinux/config" if you make " SELINUX=permissive " instead of " SELINUX=enforcing " OR disable SELinux with the help of "system-config-securitylevel"
It work on after that.
This confirms that the problem is indeed SELinux related. Anyone who can provide a better solution? -- Bazsi