summaryrefslogtreecommitdiff
path: root/doc/man/hald.8.in
blob: 3e308b2c18dc202694213d7e2e3cd7a0815bb729 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
.\" 
.\" hald manual page.
.\" Copyright (C) 2007 David Zeuthen <david@fubar.dk>
.\"
.TH HALD 8
.SH NAME
hald \- HAL daemon
.SH SYNOPSIS
.PP
.B hald
[options]

.SH DESCRIPTION

\fIhald\fP is a daemon that maintains a database of the devices
connected to the system system in real-time. The daemon connects to
the \fID-Bus\fP system message bus to provide an API that applications
can use to discover, monitor and invoke operations on devices. For
more information about both the big picture and specific API details,
refer to the \fIHAL spec\fP which can be found in
.I "@docdir@/spec/hal-spec.html"
depending on the distribution.

.SH OPTIONS
The following options are supported:
.TP
.I "--daemon=yes|no"
Specify whether to run in the foreground or the background.
.TP
.I "--verbose=yes|no"
Enable verbose debug output.
.TP
.I "--use-syslog"
Enable logging of debug output to the syslog instead of stderr. Use 
this option only together with --verbose.
.TP
.I "--help"
Print out usage.
.TP
.I "--version"
Print the version of the daemon and exit.

.SH BUGS AND DEBUGGING
.PP
Please send bug reports to either the distribution or the HAL
mailing list, see 
.I "http://lists.freedesktop.org/mailman/listinfo/hal"
on how to subscribe.

First, to obtain useful debug traces you will need to have
.B debuginfo
packages installed. On a Fedora system this is in the 
.B hal-debuginfo 
package and can be installed via the
.I yum
update program. 

Second, shut down the existing 
.B hald
daemon instance; on a Fedora system this is achieved by

.I "@sysconfdir@/init.d/haldaemon stop"

After having shut down the daemon, you might want to run

.I "pkill hald"

to ensure that all the helper processe of
.B hald
are killed too. To start the HAL daemon, use

.I "@sbindir@/hald --daemon=no --verbose=yes"

If the daemon crashes, you can start it under a debugger via

.I "gdb @sbindir@/hald"

and then typing

.I "run --daemon=no --verbose=yes"

at the 
.B "(gdb)"
prompt. To capture a back trace, use the
.B "bt"
command and attach this to the bug report.

Please also attach the output of \&\fIlshal\fR\|(1) in the bug report
if possible (it's not possible if the
.B "hald"
daemon crashed). If the nature of the bug has to do with hotplugging,
attach two outputs of \&\fIlshal\fR\|(1) - one before the device
hotplug event and one after.

.SH SEE ALSO
.PP
\&\fIudev\fR\|(7), 
\&\fIdbus-daemon\fR\|(1), 
\&\fIlshal\fR\|(1), 
\&\fIhal-set-property\fR\|(1),
\&\fIhal-get-property\fR\|(1),
\&\fIhal-find-by-property\fR\|(1),
\&\fIhal-find-by-capability\fR\|(1),
\&\fIhal-is-caller-locked-out\fR\|(1)

.SH AUTHOR
Written by David Zeuthen <david@fubar.dk> with a lot of help from many
others.