On 5/1/05, Paul paul@all-the-johnsons.co.uk wrote:
Hi,
Do you have selinux in enforcing mode?
Targetted. Had too many problems in the past with enforcing mode.
I think you are confused. Trargetted/Strict can be set to enforcing or permissive. So targetted is enabled but is it set to enforcing or permissive? check /etc/sysconfig/selinux
And you are definitely getting selinux related messages about hal. Go back at take a look at your log again... those avc messages, which were similar to what I was seeing. As soon as I put selinux in permissive mode, hal started working again. I'm expecting to see a selinux targetted policy update package to correct the problem.
-jef
Here is the bit in your log concerning selinux and hal interaction.
May 2 00:47:19 T8 kernel: audit(1114991239.938:0): avc: denied { connectto } for pid=12438 exe=/usr/libexec/hald-probe-storagepath=@ /tmp/hald-local/dbus-CBHQFkOJaq scontext=system_u:system_r:hald_t tcontext=system_u:system_r:hald_t tclass=unix_stream_socket May 2 00:47:19 T8 kernel: audit(1114991239.944:0): avc: denied { connectto } for pid=12439 exe=/usr/libexec/hald-probe-storagepath=@ /tmp/hald-local/dbus-CBHQFkOJaq scontext=system_u:system_r:hald_t tcontext=system_u:system_r:hald_t tclass=unix_stream_socket May 2 00:47:19 T8 kernel: audit(1114991239.949:0): avc: denied { connectto } for pid=12440 exe=/usr/libexec/hald-probe-storagepath=@ /tmp/hald-local/dbus-CBHQFkOJaq scontext=system_u:system_r:hald_t tcontext=system_u:system_r:hald_t tclass=unix_stream_socket