1HALD(8)                     System Manager's Manual                    HALD(8)
2
3
4

NAME

6       hald - HAL daemon
7

SYNOPSIS

9       hald [options]
10
11

DESCRIPTION

13       hald  is a daemon that maintains a database of the devices connected to
14       the system system in real-time. The daemon connects to the D-Bus system
15       message  bus  to  provide an API that applications can use to discover,
16       monitor and invoke operations on devices. For  more  information  about
17       both  the  big  picture and specific API details, refer to the HAL spec
18       which  can  be  found  in   /usr/share/doc/hal-0.5.9/spec/hal-spec.html
19       depending on the distribution.
20
21

OPTIONS

23       The following options are supported:
24
25       --daemon=yes|no
26              Specify whether to run in the foreground or the background.
27
28       --verbose=yes|no
29              Enable verbose debug output.
30
31       --help Print out usage.
32
33       --version
34              Print the version of the daemon and exit.
35
36

BUGS AND DEBUGGING

38       Please  send  bug reports to either the distribution or the HAL mailing
39       list, see http://lists.freedesktop.org/mailman/listinfo/hal on  how  to
40       subscribe.
41
42       First,  to  obtain  useful debug traces you will need to have debuginfo
43       packages installed. On a Fedora system this  is  in  the  hal-debuginfo
44       package and can be installed via the yum update program.
45
46       Second, shut down the existing hald daemon instance; on a Fedora system
47       this is achieved by
48
49       /etc/init.d/haldaemon stop
50
51       After having shut down the daemon, you might want to run
52
53       pkill hald
54
55       to ensure that all the helper processe of hald are killed too. To start
56       the HAL daemon, use
57
58       /usr/sbin/hald --daemon=no --verbose=yes
59
60       If the daemon crashes, you can start it under a debugger via
61
62       gdb /usr/sbin/hald
63
64       and then typing
65
66       run --daemon=no --verbose=yes
67
68       at  the  (gdb)  prompt. To capture a back trace, use the bt command and
69       attach this to the bug report.
70
71       Please also attach the output of lshal(1) in the bug report if possible
72       (it's  not  possible  if the hald daemon crashed). If the nature of the
73       bug has to do with hotplugging, attach two outputs of  lshal(1)  -  one
74       before the device hotplug event and one after.
75
76

SEE ALSO

78       udev(7),  dbus-daemon(1),  lshal(1), hal-set-property(1), hal-get-prop‐
79       erty(1),  hal-find-by-property(1),  hal-find-by-capability(1),  hal-is-
80       caller-locked-out(1)
81
82

AUTHOR

84       Written  by David Zeuthen <david@fubar.dk> with a lot of help from many
85       others.
86
87
88
89
90                                                                       HALD(8)
Impressum