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.14/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       --use-syslog
32              Enable  logging of debug output to the syslog instead of stderr.
33              Use this option only together with --verbose.
34
35       --help Print out usage.
36
37       --version
38              Print the version of the daemon and exit.
39
40

BUGS AND DEBUGGING

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

SEE ALSO

82       udev(7), dbus-daemon(1), lshal(1),  hal-set-property(1),  hal-get-prop‐
83       erty(1),  hal-find-by-property(1),  hal-find-by-capability(1),  hal-is-
84       caller-locked-out(1)
85
86

AUTHOR

88       Written by David Zeuthen <david@fubar.dk> with a lot of help from  many
89       others.
90
91
92
93
94                                                                       HALD(8)
Impressum