Russell Coker a scris:
On Tuesday 16 September 2008 04:12, "Eddy Petrișor" <[EMAIL PROTECTED]>
wrote:
bounty:/home/eddy# hald --daemon=no --verbose=yes
21:11:30.374 [I] hald.c:669: hal 0.5.11
21:11:30.374 [I] hald.c:734: Will not daemonize
21:11:30.374 [I] hald_dbus.c:5381: local server is listening at
unix:abstract=/var/run/hald/dbus-D3X7pfTwhT,guid=cd92ac6b97fd5842d99c518b48
cea552 21:11:30.375 [E] hald_dbus.c:5747: dbus_bus_get(): An SELinux policy
prevents this sender from sending this message to this recipient
(rejected message had interface "org.freedesktop.DBus" member "Hello"
error name "(unset)" destination "org.freedesktop.DBus")
What is the context of the hald at that time? "ps axZ" will tell you.
It seems that on system start it was running, but once stopped, it can't be
started again:
bounty:/home/eddy# hald --daemon=no --verbose=yes & ps axZ | grep hald
[1] 5081
10:06:18.189 [I] hald.c:669: hal 0.5.11
10:06:18.189 [I] hald.c:734: Will not daemonize
10:06:18.190 [I] hald_dbus.c:5381: local server is listening at
unix:abstract=/var/run/hald/dbus-qcdUjZAVcF,guid=46d0f9b541d054b4af2381ae48d0ac6a
10:06:18.191 [E] hald_dbus.c:5747: dbus_bus_get(): An SELinux policy prevents this sender from
sending this message to this recipient (rejected message had interface "org.freedesktop.DBus" member
"Hello" error name "(unset)" destination "org.freedesktop.DBus")
system_u:system_r:hald_t:s0 4006 ? Ss 0:00 /usr/sbin/hald
system_u:system_r:hald_t:s0 4007 ? S 0:00 hald-runner
system_u:system_r:hald_t:s0 4028 ? S 0:00
/usr/lib/hal/hald-addon-dell-backlight
system_u:system_r:hald_t:s0 4031 ? S 0:00 hald-addon-input: Listening on
/dev/input/event1 /dev/input/event3 /dev/input/event4 /dev/input/event5 /dev/input/event6
/dev/input/event7 /dev/input/event9 /dev/input/event11
system_u:system_r:hald_t:s0 4033 ? S 0:00
/usr/lib/hal/hald-addon-cpufreq
system_u:system_r:hald_t:s0 4034 ? S 0:00 hald-addon-acpi: listening on acpid
socket /var/run/acpid.socket
system_u:system_r:hald_t:s0 4050 ? S 0:00 hald-addon-storage: no polling on
/dev/scd0 because it is explicitly disabled
unconfined_u:system_r:hald_t:s0 5081 pts/2 Z 0:00 [hald] <defunct>
unconfined_u:unconfined_r:unconfined_t:s0 5083 pts/2 S+ 0:00 grep --colour
hald
[1]+ Exit 1 hald --daemon=no --verbose=yes
bounty:/home/eddy# /etc/init.d/hald restart
bash: /etc/init.d/hald: No such file or directory
bounty:/home/eddy# /etc/init.d/hal restart
Restarting Hardware abstraction layer: haldbounty:/home/eddy#
bounty:/home/eddy# ps axZ | grep hald
bounty:/home/eddy# tty
/dev/pts/2
If you use /etc/init.d/hald to do start it, what happens?
bounty:/home/eddy# /etc/init.d/hal start
Starting Hardware abstraction layer: haldbounty:/home/eddy#
bounty:/home/eddy# echo $?
1
--
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
