Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #590
Difficulty: Easy
In a linear search algorithm, the input size is the number of elements in the collection (n) divided by 2.
True or False?
Linux & Unix Commands - Search Man Pages

halevt(1) [debian man page]

HALEVT(1)						      General Commands Manual							 HALEVT(1)

halevt - Generic handler for HAL events SYNOPSIS
halevt [options] DESCRIPTION
Halevt is a daemon that executes arbitrary commands when a device with certain properties is added to the system and when device properties change, using HAL. Unless a configuration file is given on the command line with the -c option, configuration files are searched for in $HOME/.halevt, /etc/halevt, and /usr/share/halevt (in that order). All the files ending with .xml found in these directories are considered to be configuration files. If a file with the same name has already been found in a previous directory, it is ignored. Default for halevt is to run as a daemon in the background. Halevt may also be run in another mode, called the reporting mode, turned on by the -i option. In that case no config file is read, Halevt stays in the foreground and report all the HAL events. OPTIONS
-c file Use configuration file file. -d Give debugging informations and stay in the foreground. -f Stay in the foreground. -g group Run as group group, if started by the root user. Default is to run as halevt. -h Help message and options summary. -i Run in reporting mode. No configuration file is read, and halevt stays in the foreground, reporting all the HAL events. -p pidfile Use pid file pidfile to store the daemon pid, instead of the default. Default is /var/run/ if run as root user, and no pid file if run as a user. - means no pidfile. -u user Run as user user, if started by the root user. Default is to run as halevt. SEE ALSO
lshal(1), hald(8) VERSION
This is Halevt version AUTHOR
Main author is Patrice Dumas pertusus at free dot fr. AVAILABILITY
The latest version of this program can be found at: COPYRIGHT
Copyright (C) 2007-2008 Patrice Dumas <pertusus at free dot fr>, 2005 Novell, Inc. There is NO warranty. You may redistribute this software under the terms of the GNU General Public License; either version 2 of the License, or (at your option) any later version. For more information about these matters, see the file named COPYING. HALEVT(1)

Check Out this Related Man Page

HALD(8)                                                       System Manager's Manual                                                      HALD(8)

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 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 <> with a lot of help from many others. HALD(8)

Featured Tech Videos