hald(1M) System Administration Commands hald(1M)NAME
hald - daemon that supports hardware abstraction layer
SYNOPSIS
/usr/lib/hal/hald [--daemon={yes | no}]] [--help] [--use-syslog]
[--verbose={yes | no}] [--version]
DESCRIPTION
The hald daemon supports the recognition of hardware changes for devices that conform to the Hardware Abstraction Layer (HAL) specifica-
tion.
The enabling and disabling of hald can be performed through the service management facility (SMF) (see smf(5)). hald is managed using the
fault management resource identifier (FMRI) svc:/system/hal. Options can be specified as SMF properties. See EXAMPLES.
OPTIONS
The following options are supported:
--daemon Run as a daemon.
--help Display usage information and exit.
--use-syslog Display debug messages to syslog instead of stderr. Use this option to record debug messages if HAL runs as daemon.
--verbose Display debug information.
--version Display version information and exit.
EXAMPLES
Example 1 Specifying a Property
The following svccfg(1M) command specifies the --verbose option.
example# svccfg
svc:> select hal
svc:/system/hal> listprop hal/*
hal/verbose boolean false
hal/use_syslog boolean false
svc:/system/hal> setprop hal/verbose=true
svc:/system/hal> exit
FILES
/usr/lib/hal HAL-related files
/etc/hal/fdi Device information files
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWhalr |
+-----------------------------+-----------------------------+
|Interface Stability |Volatile |
+-----------------------------+-----------------------------+
SEE ALSO svccfg(1M), attributes(5), hal(5), smf(5)SunOS 5.11 2 Jul 2008 hald(1M)
Check Out this Related Man Page
HALD(8) System Manager's Manual HALD(8)NAME
hald - HAL daemon
SYNOPSIS
hald [options]
DESCRIPTION
hald is a daemon that maintains a database of the devices connected to the system system in real-time. The daemon connects to the D-Bus
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 HAL spec which can be found in /usr/share/doc/hal-doc/spec/hal-spec.html
depending on the distribution.
OPTIONS
The following options are supported:
--daemon=yes|no
Specify whether to run in the foreground or the background.
--verbose=yes|no
Enable verbose debug output.
--use-syslog
Enable logging of debug output to the syslog instead of stderr. Use this option only together with --verbose.
--help Print out usage.
--version
Print the version of the daemon and exit.
BUGS AND DEBUGGING
Please send bug reports to either the distribution or the HAL mailing list, see http://lists.freedesktop.org/mailman/listinfo/hal on how to
subscribe.
First, to obtain useful debug traces you will need to have debuginfo packages installed. On a Fedora system this is in the hal-debuginfo
package and can be installed via the yum update program.
Second, shut down the existing hald daemon instance; on a Fedora system this is achieved by
/etc/init.d/haldaemon stop
After having shut down the daemon, you might want to run
pkill hald
to ensure that all the helper processe of hald are killed too. To start the HAL daemon, use
/usr/sbin/hald --daemon=no --verbose=yes
If the daemon crashes, you can start it under a debugger via
gdb /usr/sbin/hald
and then typing
run --daemon=no --verbose=yes
at the (gdb) prompt. To capture a back trace, use the bt command and attach this to the bug report.
Please also attach the output of lshal(1) in the bug report if possible (it's not possible if the hald daemon crashed). If the nature of
the bug has to do with hotplugging, attach two outputs of lshal(1) - one before the device hotplug event and one after.
SEE ALSO udev(7), dbus-daemon(1), lshal(1), hal-set-property(1), hal-get-property(1), hal-find-by-property(1), hal-find-by-capability(1), hal-is-
caller-locked-out(1)AUTHOR
Written by David Zeuthen <david@fubar.dk> with a lot of help from many others.
HALD(8)